Make DOTNET_DbgEnableMiniDump and DOTNET_DbgMiniDumpType consistent across all single-file form factors

[steveisok]

Currently, different single-file form factors handle dump generation inconsistently:

Regular single-file apps only support full dumps and show an error message if other dump types are requested
NativeAOT apps now support custom createdump paths via DOTNET_DbgCreateDumpToolPath
We should standardize the behavior across all single-file form factors to provide a consistent developer experience.

Follow up issue created out of #122989

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• DbgEnableMiniDump does not work with PublishSingleFile #101957
• Issues with memory dumps and Single File App #107344