Release 2.0.0

[gonzalocasas]

This PR prepares the release of roslibpy 2.0.0, using the newly updated release workflow that would release once the tag is pushed to main. I have also removed the test step during the local release push, because now this is consistently done on the PR instead, and locally, it means one would need to run ROS 1 and ROS 2 at the same time, and the tests are not configured for that, they need to be run in sequence, composing up and down ROS 1 and 2 one after the other.

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: release

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 check).
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate)

Fixes #140

[gonzalocasas]

@sea-bass @EzraBrooks everything should be ready for the new release. If the CI workflow triggers correctly as expected, once this PR is merged into main, the release should be built and pushed to pypi from that tag. If any of you can give the green light for it, we merge and hopefully get this finally out there! ;)

[sea-bass]

Cool! Looks like PyPi is updated. Thanks @gonzalocasas