Improve performance of the geo promote command

In !5401 (merged) we added a new geo promote command, but the performance is very slow when running on a puma/rails node. This is because it currently runs a command via rails runner to check whether the current node is a secondary node.

We should look at improvements that do not require rails runner, and booting up the entire rails environment.

We could use a small active record script like we do in : https://gitlab.com/gitlab-org/omnibus-gitlab/-/blob/master/files/gitlab-cookbooks/gitlab/libraries/helpers/gitlab_rails_env_helper.rb

Or possible make a call to rails dbconsole (not sure how quick this is)

Or explore some other option.