Remove `defaults` from test_and_deploy.yml

[sfmig]

Description

What is this PR

• [ ] Bug fix
• [x] Addition of a new feature
• [ ] Other

Why is this PR needed? We are currently using the defaults channel in our actions, which from Aug2024 is not free to use for our case

What does this PR do? Add nodefaults channel to prevent from using the defaults channel. See docs

References

\

How has this PR been tested?

The CI in this PR shows the default channel is omitted.

Is this a breaking change?

No.

Does this PR require an update to the documentation?

Should we include this in our docs for our users?

Checklist:

• [ n/a ] The code has been tested locally
• [ n/a ] Tests have been added to cover all new functionality
• [ ] The documentation has been updated to reflect any changes
• [x] The code has been formatted with pre-commit

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.77%. Comparing base (abeaff1) to head (af3a910). Report is 1 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #275 +/- ## ======================================= Coverage 99.77% 99.77% ======================================= Files 14 14 Lines 883 883 ======================================= Hits 881 881 Misses 2 2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[adamltyson]

Probably not? I'd say it's not our job to tell everyone how to configure conda.

I would say our job ends once we've pointed users in the right direction. I.e. we should recommend miniforge, but not miniconda. Other than that, it's up to them. Based on recent comments from Anaconda, I don't even know who can and can't use the default channels for free anymore anyway!

[niksirbi]

Probably not? I'd say it's not our job to tell everyone how to configure conda.

I would say our job ends once we've pointed users in the right direction. I.e. we should recommend miniforge, but not miniconda. Other than that, it's up to them. Based on recent comments from Anaconda, I don't even know who can and can't use the default channels for free anymore anyway!

Our installation instructions begin by assuming people already have conda/mamba installed. Do you recommend mentioning to install conda via miniforge (in case they don't already have it installed)?

[adamltyson]

Our installation instructions begin by assuming people already have conda/mamba installed. Do you recommend mentioning to install conda via miniforge (in case they don't already have it installed)?

I think that's fine. I think we should just recommend miniforge if we recommend a distribution.