fix: ensure API key values are converted to strings in Postman collec…

[pooja-bruno]

Description

When importing an API key authentication with a key and value, the value is now explicitly converted to a string. This conversion is necessary because Postman's schema does not strictly define the type of the value, allowing it to be modified to anything by directly editing the JSON.

PM Schema:

{
  "type": "object",
  "title": "Auth",
  "$id": "#/definitions/auth-attribute",
  "description": "Represents an attribute for any authorization method provided by Postman. For example `username` and `password` are set as auth attributes for Basic Authentication method.",
  "properties": {
    "key": {
      "type": "string"
    },
    "value": {},
    "type": {
      "type": "string"
    }
  },
  "required": [
    "key"
  ]
} 

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

[sanish-bruno]

Is there any chance that the value can be null or undefined and we are trying accessnull.toString() ?

[pooja-bruno]

Hey @sanish-bruno! that might be possible so I've added a check for that authValues.value?.toString() to handle potential null or undefined cases.