Move creation of env.yaml outside the current directory

[davidwendt]

Description

Moves the creation of the env.yaml file in build scripts to a temporary directory instead of the current directory.

During the CI builds, a env.yaml file is created for use with a mamba call later in the script. This is a problem when trying to reproduce CI locally when the launched docker container tries to create this file locally as root. If the user does not have root access (or equivalent permissions), the file is not created and the process aborts.

The same error occurs when creating the test_results directory when the RAPIDS_TEST_DIR is not set. In this case the script tries to create the test_results in the current working directory.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[vyasr]

Could we port this change to other repos as well? We have a new tool rapids-reviser that can help automate that change, @bdice could probably show you how to set this up (although scripting this change is slightly nontrivial relative to our usual since this isn't just a single sed replacement but also a new line addition).

[raydouglass]

Not strictly necessary since these scripts almost always run in a container, but cleaning up temp directories isn't a bad idea.

Suggested change

	ENV_YAML_DIR="$(mktemp -d)"
	ENV_YAML_DIR="$(mktemp -d)"
	trap 'rm -rf -- "$ENV_YAML_DIR"' EXIT

[ajschmidt8]

Aren't temp directories cleared on boot automatically? I'd vote to omit this extra line to keep things as succinct as possible.

[ajschmidt8]

Plus like you mentioned, 99% of the time, these scripts are run in containers.

[ajschmidt8]

thanks David

[vyasr]

I'm fine with getting this merged ASAP, but could we open an issue to track #14476 (comment)?

[davidwendt]

/merge