feat: added export option to secrets env #342

[Sooryasanand]

Description

I have introduced an export flag in options.ts to determine whether the export keyword should be prefixed to environment variables for shell usage. This is relevant for Unix-based systems, where export is required to make the variables available to child processes. On Windows, however, the export keyword or an equivalent is unnecessary because a child process automatically inherits the environment variables of its parent process. This behavior is documented on the official Microsoft website: Environment Variables.

Issues Fixed

• Fixes Add export formats to secrets env command #342

Tasks

• 1. Add export option for json
• 2. Add Tests

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[CMCDragonkai]

If review comments are fixed, resolve the threads with a comment, don't leave it open.

[aryanjassal]

I have gone through the PR and made any required changes. Linting gives the all-clear, and the tests are also all passing. This should now be ready for merging.

[CMCDragonkai]

Can someone add a comment to #342 explaining what this PR brings in from a UI/UX perspective.

[CMCDragonkai]

Also not all conversations here have been resolved.

[CMCDragonkai]

@aryanjassal #342 or @Sooryasanand please summarise the feature in #342.