feat(install.sh): change default target directory for Apple Silicon

[SCKevinO]

Fix #611

• Add a changelog entry in the section "To Be Released" of CHANGELOG.md

[EtienneM]

Thanks :)

[josephpage]

Hello, sorry I'm only reading the PR now, but I'm wondering about using a folder that only exists when Homebrew is installed for an install script that's going to be used by those who don't usually use Homebrew and on whom it probably won't be installed. Or maybe I'm missing something and I'm sorry to bother you.

[SCKevinO]

Hello, Homebrew is pretty common for developers on mac, it seemed like a good fit for a default value and the install script will create the folder if it doesn't exist already. In that case, the problem will be that the folder is not in the PATH.
If you want to change the install folder location, you can do so with the -i option.

[josephpage]

Thanks for the reply, I understand your reasoning better.
Installing a binary in a directory managed by Homebrew could lead to an error during a future installation with Homebrew. That's my only concern.

In fact, Homebrew is so popular on the Mac that most tools now only offer installation with Homebrew or with an nerdy alternative method for those who want full control : a binary to download and move yourself. For example:

• Github CLI: https://github.com/cli/cli#installation
• kubectl : https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/
• Heroku : https://devcenter.heroku.com/articles/heroku-cli#install-with-an-installer
• Scaleway CLI : https://github.com/scaleway/scaleway-cli#homebrew
• Terraform : https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli#install-terraform
• jq : https://jqlang.github.io/jq/download/
  And the list goes on...

The cleanest solution might even be to deprecate this install script for Macs in favor of the Homebrew formula.