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

[Sooryasanand]

The if statement applies to Unix systems. On Windows, an equivalent check is unnecessary because the export keyword (or equivalent) isn’t needed. On Windows, child processes automatically inherit the parent process's environment variables, as documented on the official Microsoft website: Environment Variables.

[aryanjassal]

If that is the case, then instead of making this an option, we can probably make this another env format - something like --env-format unix-export. Or we can also rename this to be --env-format unix-local for non-export and --env-format unix-global for exported environment variables. Thoughts, @CMCDragonkai?