Adding spcqe recipe

[pluflou]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/spcqe) and found it was in an excellent condition.

[synapticarbors]

The error on this one is strange. pip check is failing with:

+ pip check
spcqe 0.0.1a0 requires cvxpy, which is not installed.

but if you look at the output of what's being installed it includes:

cvxpy:            1.5.1-py312h7900ff3_0               conda-forge
cvxpy-base:       1.5.1-py312h266a736_0               conda-forge

See: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=936210&view=logs&j=6f142865-96c3-535c-b7ea-873d86b887bd&t=22b0682d-ab9e-55d7-9c79-49f3c3ba4823&l=881

@conda-forge/staged-recipes -- does anyone else understand what might be going wrong here?

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[pluflou]

@synapticarbors seems likely a cvxpy packaging issue--I opened an issue here. Meanwhile I plan to adjust the tests in the recipe to move this along but I haven't gotten to it yet.

[pluflou]

I pinned the cvxpy version to the latest that works with conda until issue #2447 is resolved. @conda-forge/help-python this ready for review!

[synapticarbors]

@pluflou -- Sorry for the delay getting back to you on this. I would actually suggest commenting out the pip check until the upstream issue is fixed. We probably don't want to pin a package to a specific version when it's not in the upstream version requirements. You could then re-enable the pip check when the issue with cvxpy is fixed.

[pluflou]

@synapticarbors makes sense. Done! Thank you :)