Planning scene viz

[gonzalocasas]

This change (finally) adds supports for all the planning scene elements to be visualized with the default Robot Visualize component of Grasshopper. This means both attached and non-attached collision meshes will be retrieved and shown and there's no need to pass them to the component explicitly anymore.

Here's a quick screenshot showing the component in action with both an ACM and a CM:

It also changes the behavior of the Attach tool component that was (needlessly) adding the tool meshes to the planning scene, but they can be an in-memory thing only.

And a bunch of typos as well.

What type of change is this?

• [x] Bug fix in a backwards-compatible manner.
• [x] New feature in a backwards-compatible manner.
• [ ] 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.rst 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).
• [ ] 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)

[gonzalocasas]

After updating flake8, there were a bunch of additional lint errors, so, the last commit is a black formatting of two files to fix those.

[gonzalocasas]

add a pyproject.toml with

+1 to that!