Allow to configure cpus, memory, disk size and pull-secret file location when creating new cluster

[dgolovin]

Form to create OpenShift Local cluser is empty right now. Would be good to have:

1. Makrdown property with short explanation where those configuration values coming from with link to open extension settings and external documentation
2. Cpus, memory, disk size and optional pull-secret file location fields initialized by default from extension settings

Additional context

  -c, --cpus int                  Number of CPU cores to allocate to the instance (default 2)
  -d, --disk-size uint            Total size in GiB of the disk used by the instance (default 31)
  -m, --memory int                MiB of memory to allocate to the instance (default 4096)
  -p, --pull-secret-file string   File path of image pull secret (download from https://console.redhat.com/openshift/create/local)

[gbraad]

Form to create OpenShift Local cluser is empty right now

As we prioritize crc config set (Configuration) over any other way to provide the settings. Providing them with the start command is a one-shot and not persisted for a recreation. We mostly noticed that people to use the same settings again and again.

So if you add a dialog, you would have to provide the defaults and/or the settings as configured. Defaults are enforced based on the preset... they are currently enforced in a single location (configuration dialog).

Take note, any parameter for crc start is not a guarantee to work from the extension, as the extension relies on the use of the API endpoint:

https://github.com/crc-org/crc/blob/813c80a473046247eb232bb7e9e3da79a954118b/pkg/crc/api/handlers.go#L119-L134

Note: I would not provide most of them besides those you mentioned, as NameServer is a special case, SharedDirs not actively advertised for Windows, etc.

[lstocchi]

Closing. It was fixed by #228