feat: add docs for metadata in config file

[officialasishkumar]

What has changed?

Please include a summary of the change.

This PR Resolves keploy/keploy#2817

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Documentation update (if none of the other choices apply).

How Has This Been Tested?

Please run npm run build and npm run serve to check if the changes are working as expected. Please include screenshots of the output of both the commands. Add screenshots/gif of the changes if possible.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.

[Copilot]

Pull Request Overview

This PR adds documentation for the new --metadata flag for the keploy record command, providing users with examples and usage details for adding key-value metadata entries in the config file.

• Updated the CLI commands table to include the --metadata flag.
• Added detailed usage examples and description for the --metadata flag.

Comments suppressed due to low confidence (1)

versioned_docs/version-3.0.0/running-keploy/cli-commands.md:75

• [nitpick] Consider clarifying the expected format for metadata key-value pairs, including details on separators, escaping rules (if any), and allowed characters, to help users avoid input errors.

- `--metadata string` - Key-value pairs to be added as metadata in the config.yaml file. If a `name` key is provided, it will be used as the test set name.