Don't build conda store cli

[soapy1]

part 2 to address #911

Description

This PR removes steps for building and releasing conda-store (the cli). This includes:

• removing the split package from the conda build recipe - now the recipe will just build the conda-store-server
• Removing conda-store (cli) build tasks from the CI (this also removes the release build tasks)
• Removing conda-store integration tests from the CI
• Removing conda-store steps from cut-release-pr script

Pull request checklist

• Did you test this change locally?
• Did you update the documentation (if required)?
• Did you add/update relevant tests for this change (if required)?

[netlify]

✅ Deploy Preview for conda-store ready!

Name	Link
🔨 Latest commit	261bbcc
🔍 Latest deploy log	https://app.netlify.com/sites/conda-store/deploys/678035ab88ffb7000868380b
😎 Deploy Preview	https://deploy-preview-1019--conda-store.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[trallard]

Thank you @soapy1 this is going in the right direction, I think since you are already going through removing the build for conda-store (cli) we might as well refactor the workflows to remove redundant matrix bits

[trallard]

Another thought we would need to add a note somewhere about stopping releasing the cli as a separate package

[soapy1]

Another thought we would need to add a note somewhere about stopping releasing the cli as a separate package

There are a few public places that users will be able to see this change:

• this pr
• release notes (for the next release)
• pr to conda-forge package that removes the conda-store package

I think release notes is an appropriate place to be broadcasting this change to communicate with users that this change is coming.

Are there any other stream of news that a conda-store user would be looking at to get this type of information?

[peytondmurray]

Looks great. Did the recipe/meta.yaml just come from the conda-store-server conda package?

EDIT: Just saw that they were un-nested from the outputs section. Sorry!

[soapy1]

Did the recipe/meta.yaml just come from the conda-store-server conda package?

Nope, I edited it for this PR. We'll need to update the conda-store-server package to match this for next release though.

[trallard]

If we are not building the Docker image shall we also remove the Dockerfile?
There does not seem to be a reason to keep straggling files.

[soapy1]

I would say it would be better to remove all the conda-store directory at the same time opposed to piecemeal removing pieces.

[trallard]

There are a lot of places where we use conda-store-server, which might change as we consolidate the packages. I suggest setting a job-level env variable for this and reusing the variable instead.

[soapy1]

I think the amount of effort it will take to introduce a job-level variable will be pretty similar to the amount of effort it will take to explicitly rename things. Since (1) we should only be renaming conda-store-server -> conda-store once, and (2) it is easier to read + debug yaml files (and ci) that use explicit names opposed to variables, I would prefer not to introduce this variable.

But open to doing it if I'm missing an important upside that it will provide. I think it would be appropriate to do that work in a follow up PR