Improve Kubernetes agent documentation

What does this MR do?

• unified examples to gitlab-kubernetes-agent as all examples where a mix of gitlab-kubernetes-agent, gitlab-agent & <YOUR_NAMESPACE>
• added # - grpc://host.docker.internal:5005 # use this when connecting from within Docker e.g. from kind to existing examples
• added # - wss://kas.gitlab.com to existing examples
• added section how to remove the agent

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because this change is docs-only.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

doc/user/clusters/agent/index.md

@@ -169,6 +169,7 @@ the Agent in subsequent steps. You can create an Agent record with GraphQL:
     }
   }
   ```
+  
   **_NOTE:_** GraphQL only displays the token & ids one time after creating it. Please note down the `secret`, `clusterAgentId` & `clusterAgentTokenId`
 
   If you are new to using the GitLab GraphQL API, refer to the
@@ -214,7+215,7 @@
 
 Otherwise, you can follow below for fully manual, detailed installation steps.
 
 ##### Create the Kubernetes secret
 
 After generating the token, you must apply it to the Kubernetes cluster.
 
@@ -245,7+246,7 @@
     In this case, you may specify `kas-address` value as
     `grpc://gitlab-kas.<your-namespace>:5005`) to use gRPC directly, where `gitlab-kas`
     is the name of the service created by `gitlab-kas` chart, and `your-namespace`
     is the namespace where the chart was installed. Encrypted gRPC is not supported yet.
     Follow the
     [Support TLS for gRPC communication issue](https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/7)
     for progress updates.
@@ -532,7+533,7 @@
 
 This error is shown if you configured `wss` as `kas-address` on the agent side,
 but KAS on the server side is not available via `wss`. To fix it, make sure the
 same schemes are configured on both sides.
 
 It's not possible to set the `grpc` scheme due to the issue
 [It is not possible to configure KAS to work with `grpc` without directly editing GitLab KAS deployment](https://gitlab.com/gitlab-org/gitlab/-/issues/276888). To use `grpc` while the