Fix geo-install script

What does this merge request do and why?

Fixes the geo-install script. It is broken in CI and for developers.

Also copies a bunch of changes from the non-Geo install script for parity.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. Stop any GDKs
2. Change to a temp directory
3. Run:

export GITLAB_LICENSE_KEY=$(cat ~/path/to/your/license/file)

curl "https://gitlab.com/gitlab-org/gitlab-development-kit/-/raw/fix-geo-install/support/geo-install" | bash -s gdk gdk2 fix-geo-install mise && \
cd gdk/gitlab && \
git remote set-url origin git@gitlab.com:gitlab-org/gitlab.git && \
bundle exec lefthook install && \
cd .. && \
git remote set-url origin git@gitlab.com:gitlab-org/gitlab-development-kit.git && \
gdk config set webpack.enabled false && gdk config set vite.enabled true && gdk config set vite.hot_module_reloading false && \
gdk reconfigure && \
gdk restart && \
cd ../gdk2 && \
git remote set-url origin git@gitlab.com:gitlab-org/gitlab-development-kit.git && \
gdk config set webpack.enabled false && gdk config set vite.enabled true && gdk config set vite.hot_module_reloading false && \
gdk config set vite.port 3809 && \
gdk reconfigure && \
gdk restart

It should install 2 GDKs and configure Geo.

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This MR references an issue describing the change.
• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.