Bump to 0.3.3

[joburger]

Testing version bump and pip workflow

What type of change is this?

• [ ] Bug fix in a backwards-compatible manner.
• [ ] New feature in a backwards-compatible manner.
• [ ] Breaking change: bug fix or new feature that involve incompatible API changes.
• [X] Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [ ] I added a line to the CHANGELOG.rst file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• [ ] I ran all tests on my computer and it's all green (i.e. invoke test).
• [ ] I ran lint on my computer and there are no errors (i.e. invoke lint).
• [ ] I added new functions/classes and made them available on a second-level import, e.g. compas.datastructures.Mesh.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] I have added necessary documentation (if appropriate)

[gonzalocasas]

👍 The conda recipe is now building almost correctly: https://github.com/conda-forge/staged-recipes/pull/14403 The remaining issue is unrelated, and will be fixed at the end of the week with the next release of COMPAS

[gonzalocasas]

@joburger I think this has not been merged yet.

[joburger]

@joburger I think this has not been merged yet.

true, oops! my bad