Update documentation with new authenticate usage on the CLI (#2865)

* docs: update deploy-and-login getting started guide with new authenticate usage

* docs: update api-clients/cli.mdx to remove login-name flag when using authenticate

* docs: update common-workflows/manage-users-groups.mdx to remove login-name flag when using authenticate

* docs: update common-workflows/workflow-ssh-proxycommand.mdx with new short form usage of authenticate command when using the primary auth method in the global scope

* docs: update oss/installing/no-gen-resources.mdx to remove login-name usage in authenticate command

* docs: update oss/installing/run-and-login.mdx with short form usage of boundary authenticate

* docs: fix tabs

* docs: fix numbering

* Apply batch of suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* docs: fix code blocks

* fixes code blocks

---------

Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
Co-authored-by: stellarsquall <stellarsquall@protonmail.ch>

website/content/docs/api-clients/cli.mdx

@@ -32,9 +32,8 @@ The following shows use of the [`-addr`](/boundary/docs/api-clients/cli#addr) fl
 
 ```shell-session
 $ boundary authenticate password \
-    -addr=https://boundary.example.com:9200
-    -auth-method-id=ampw_1234567890 \
-    -login-name=admin
+    -addr=https://boundary.example.com:9200 \
+    -auth-method-id=ampw_1234567890
 ```
 
 Instead of specifying the `-addr` flag for every command, you can set an environment variable `BOUNDARY_ADDR=https://boundary.controller.com:9200`.