Update website with new password rules taken into account (#2330)

* Update website with new password rules taken into account

* Remove the prompt examples as it messes up copying

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

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

website/content/docs/common-workflows/manage-users-groups.mdx

@@ -116,7 +116,7 @@ the attributes for the auth method, if desired.)
 
 
 ```bash
-boundary accounts create password -auth-method-id ampw_PbE6nNT72a -login-name 'myuser' -password supersecure -name my_account -description 'My password account'
+boundary accounts create password -auth-method-id ampw_PbE6nNT72a -login-name 'myuser' -name my_account -description 'My password account'
 
 Account information:
   Auth Method ID:      ampw_PbE6nNT72a
@@ -283,7 +283,7 @@ Now you can test logging in.
 
 
 ```bash
-$ boundary authenticate password -login-name myuser -password supersecure -auth-method-id ampw_PbE6nNT72a
+$ boundary authenticate password -login-name myuser -auth-method-id ampw_PbE6nNT72a
 ```
 
 </Tab>

website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx

@@ -36,7 +36,7 @@ Before `ssh` can invoke `boundary connect` you need to authenticate. In this exa
 default username (admin) and password (password):
 
 ```bash
-$ boundary authenticate password -login-name=admin -password password -auth-method-id=ampw_1234567890
+$ boundary authenticate password -login-name=admin -auth-method-id=ampw_1234567890
 ```
 
 ## SSH to Target
@@ -117,7 +117,7 @@ Before `ssh` can invoke `boundary connect` you need to authenticate. In this exa
 default username (admin) and password (password):
 
 ```bash
-$ boundary authenticate password -login-name=admin -password password -auth-method-id=ampw_1234567890
+$ boundary authenticate password -login-name=admin -auth-method-id=ampw_1234567890
 ```
 
 ## Authorize the Session

website/content/docs/getting-started/deploy-and-login.mdx

@@ -93,8 +93,7 @@ HCP Boundary instance.
 ```shell-session
 $ boundary authenticate password \
    -auth-method-id=COPIED_AUTH_ID \
-   -login-name=ADMIN_USERNAME \
-   -password=ADMIN_PASSWORD
+   -login-name=ADMIN_USERNAME
 ```
 
 You are now logged into your HCP Boundary instance's Global scope via the CLI.

website/content/docs/oss/installing/no-gen-resources.mdx

@@ -232,7 +232,6 @@ Create a login account for the auth method.
 $ boundary accounts create password \
   -recovery-config /tmp/recovery.hcl \
   -login-name "myuser" \
-  -password "foofoofoo" \
   -auth-method-id <auth_method_id_from_last_step>
 ```
 
@@ -484,6 +483,5 @@ resource "boundary_role" "project_admin" {
 ```bash
 boundary authenticate password \
   -auth-method-id <auth_method_id> \
-  -login-name myuser \
-  -password foofoofoo
+  -login-name myuser
 ```

website/content/docs/oss/installing/run-and-login.mdx

@@ -26,7 +26,6 @@ dev mode. These can be overridden, or randomly generated, with flags to
 ```
 $ boundary authenticate password \
          -login-name=admin \
-         -password password \
          -auth-method-id=ampw_1234567890
 ```