COMPAS 2.x compatibility

[gonzalocasas]

Update fab to COMPAS 2.x

What type of change is this?

• [ ] Bug fix in a backwards-compatible manner.
• [ ] New feature in a backwards-compatible manner.
• [x] Breaking change: bug fix or new feature that involve incompatible API changes.
• [ ] 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.

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

[yck011522]

@gonzalocasas Regarding the ur10e sample data. Do you want to use the new script to generate that package. The folder structure is not the same as the existing one.

Refer to : #406

See my new commit for the UR10e: https://github.com/compas-dev/compas_fab/pull/406/commits/4ed1b37c8d404c5114ab399168ad5c57992062bf

The visual and collision mesh folders does not have support folder

[gonzalocasas]

Except the blender parts, I think everything else has been addressed, so I will go ahead and merge this one! Thanks @chenkasirer and @yck011522 !!