update parameters in build_ghuser_components

[beverlylytle]

ATM this is for my convenience. Shouldn't be merged until compas_ghpython.get_grasshopper_plugin_path is released in the next version of compas.

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.
• [ ] 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_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)

[beverlylytle]

Should a similar change be made in compas, that is, adding the components/ghuser dir? and its cleanup?

[beverlylytle]

Sorry, this PR is growing in scope. I wanted to clean up the VisualizeRobot component, but doing that is too annoying without the other changes in this PR. So I piggybacked...