maint: Cancel activation script removal

[jjerphan]

As discussed in #2524.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@aaae25f). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3946   +/-   ##
=======================================
  Coverage        ?   63.66%           
=======================================
  Files           ?      303           
  Lines           ?    37968           
  Branches        ?     2828           
=======================================
  Hits            ?    24171           
  Misses          ?    13742           
  Partials        ?       55           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jjerphan]

@ndevenish: does this look good to you?

[ndevenish]

This solves the problem, insofar as it's removing the new notice.

Eventually removing the file might be valuable in terms of simplicity, if it is truly redundant; although I suspect you would inevitably get a constant drip-feed of asking why there is a conda.sh and not a mamba.sh.

I don't know how much was deliberate done and how much came naturally out of rewriting the notice, but I feel that the WARNING: This is required for mamba to work correctly as of 2.0. part of the new warning might be valuable? It's not just a "This is missing", it's a "this is why it is now required when it wasn't before". Feels a bit more actionable?

[jjerphan]

I feel that the WARNING: This is required for mamba to work correctly as of 2.0. part of the new warning might be valuable?

Setting MAMBA_ROOT_PREFIX would be required if the script is removed, but it won't be required anymore since the script sets it.

Would simply reverting it to using the previous script work for you?

[jjerphan]

I think that I misread your comment, this should be fixed now.