feat(kubectl): support specifying profile name when installing control planes

[jijiechen]

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • N/A
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS
  • Confirmed
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Tested with unit tests and manual tests
  • Don't forget ci/ labels to run additional/fewer tests
    • Done
• Do you need to update UPGRADE.md?
  • No
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)
  • No

Two features are included:

• Added the ability to specify a profile name that has been supported by a builtin values.{profile}.yaml.
• Provided a production profile for Kuma so that:
  • resources claims are generally higher than the default demo proifle
  • make resource requests/limits to be identical so that pod will be guaranteed on clusters
  • autoscalling is open
  • pod disruption budgets are open

[lahabana]

Do we need this in the end?