Install envoy.exe into ProgramData/envoy/bin

[codefromthecrypt]

Title: Install envoy.exe into ProgramData/envoy/bin

Description:
Right now, in the envoy-windows image, envoy.exe installs into Program Files/envoy/envoy.exe

While this does match historic install directories, choosing this makes tooling more difficult as for example make struggles with spaces.

It would be easier to install into ProgramData/envoy/bin/envoy.exe similar to the Chocolatey package manager: ProgramData/chocolately/bin/choko.exe.

Doing so wouldn't be completely unconventional, in other words, and we already write files to this directory, ex. ProgramData/envoy/envoy.yaml

[mattklein123]

cc @envoyproxy/windows-dev

[davinci26]

I am not opposed to this. I actually do agree that having spaces on the path is a bit annoying. It is a breaking change though.

@wrowe thoughts?

[codefromthecrypt]

here's the link from chocolatey explaining their choice https://docs.chocolatey.org/en-us/faqs#why-doesnt-a-package-install-software-to-program-files

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[rectified95]

I'd like to pick up this issue as a way of getting started contributing to the repo. Do people have any reservations about moving forward with this change?

cc @wrowe @mattklein123 @codefromthecrypt
Who else can I tag to gather opinions?