add inheritEnv action parameter

[OmarTawfik]

Upon some further discussion and great insights from @jkeech, I think an opt-in experience (i.e. autoEnv or inerhitEnv) could make good sense. This way it doesn't change the default experience / dev container expectations for all scenarios, but it'd be a helpful option in ones such as those detailed above. And if env was used, it could be treated as an override to anything that was automatically inherited.

Originally posted by @bamurtaugh in #242 (comment)

[OmarTawfik]

cc @bamurtaugh and @stuartleeks

[chrmarti]

Great, thanks!

Could you also add it to:

• the table in azdo-task/README.md
• azdo-task/DevcontainersCi/task.json
• the table in docs/azure-devops-task.md

[OmarTawfik]

@chrmarti done. Thanks.

[OmarTawfik]

@chrmarti done. Thanks.

[chrmarti]

Great, thanks!

[chrmarti]

CI seems stuck, closing and reopening to trigger a new run.

[chrmarti]

CI failed with:

      DataCloneError: [object Object] could not be cloned.
  
        53 |
        54 | 	test('inherits process env when asked', () => {
      > 55 | 		const originalEnv = structuredClone(process.env);
           | 		                    ^
        56 | 		try {
        57 | 			process.env = {TEST_ENV1: 'value1'};
        58 | 			const input = ['TEST_ENV2=value2'];
  
        at Object.<anonymous> (__tests__/envvars.test.ts:55:23)

[OmarTawfik]

@chrmarti fixed test by removing structuredClone(). The old object is preserved.
Thanks!

[OmarTawfik]

@chrmarti can you please tell me when does this get released?
The last release was 3 months ago.
Thanks!

[OmarTawfik]

Is it possible to ship a new release for this? unfortunately this repo cannot be imported/used from source. Thanks!
cc @bamurtaugh or @DonJayamanne

[Sam13]

Is it possible to ship a new release for this? unfortunately this repo cannot be imported/used from source. Thanks! cc @bamurtaugh or @DonJayamanne

+1