Split shell init and activation of test environment to remove spurious warning - #475

/**
 * Append activation commands to all shell profile files so that
 * subsequent workflow steps start with the correct environment active.
 *
 * This must be called AFTER the target environment has been created,
 * otherwise `.bat` wrappers (which source `conda_hook.bat`) would try
 * to activate a non-existent environment during setup and emit false
 * warnings (see #474).
 *
 * @param inputs - The parsed action inputs.
 * @param options - The current dynamic options.
 */
export async function condaInitActivation(
  inputs: types.IActionInputs,
  options: types.IDynamicOptions,
): Promise<void> {
  const isValidActivate = !(await isDefaultEnvironment(
    inputs.activateEnvironment,
    inputs,
    options,
  ));
  const autoActivateDefault: boolean =
    options.condaConfig.auto_activate === "true";
  const installationDirectory = condaBasePath(inputs, options);

  // PowerShell profiles
  // NOTE: Using array.join() to prevent auto-formatters from adding indentation
  const powerLines: string[] = [
    "",

  const isValidActivate = !(await isDefaultEnvironment(
    inputs.activateEnvironment,
    inputs,
    options,
  ));
  const autoActivateDefault: boolean =
    options.condaConfig.auto_activate === "true";
  const installationDirectory = condaBasePath(inputs, options);

  // PowerShell profiles
  // NOTE: Using array.join() to prevent auto-formatters from adding indentation
  const powerLines: string[] = [
    "",
    "# ----------------------------------------------------------------------------",
  ];
  if (isValidActivate) {
    powerLines.push(
      "# Conda Setup Action: Custom activation",
      `conda activate "${inputs.activateEnvironment}"`,
    );