--experimental-https default mkcert binary location should be changed/flexible

[jugarucristi]

Goals

1. Allow enterprise use of the feature, as many organizations block any executables stored in Appsettings from running

Non-Goals

No response

Background

The reason for this request: changing organizational policies to allow executables running from inside Appsettings for any member that may want to experiment with the flag is cumbersome.

Current alternatives: I haven't found any workarounds for this issue.

Proposal

As a quick workaround I'd store the mkcert binary inside the certificates folder instead of Appdata, or maybe there could be a command line argument for the location of the mkcert binary.