Adding emphasis to steps (#873)

<!-- Explain the changes introduced in your PR -->
A couple customers are getting confused and using both env vars and cody
auth login to authenticate with the CLI leading to undesirable effects.
This change adds emphasis for customers getting started with CLI

## Pull Request approval

You will need to get your PR approved by at least one member of the
Sourcegraph team. For reviews of docs formatting, styles, and component
usage, please tag the docs team via the #docs Slack channel.

Author: airamare01

docs/cody/clients/install-cli.mdx

@@ -98,8 +98,8 @@ export SRC_ENDPOINT=ENDPOINT
 export SRC_ACCESS_TOKEN=ACCESS_TOKEN
 cody auth login # stores the access token securely
 ```
-You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`.
-Subsequent command invocation will use the stored access token.
+<Callout type="info">You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`.
+Subsequent command invocation will use the stored access token.</Callout>
   </Tab>
 </Tabs>
 
@@ -112,7 +112,8 @@ cody auth whoami
 
 ## Authenticate with only environment variables
 
-Skip this step if you have already authenticated with the `cody auth login` command.
+**Skip this step if you have already authenticated with the `cody auth login` command.**
+
 
 If you prefer not to let Cody CLI store your access token, you can also pass the endpoint URL and access token through the environment variables `SRC_ENDPOINT` and `SRC_ACCESS_TOKEN`.