Finalize ROS2 Migration

[Cakem1x]

The humble branch currently tracks the latest move base flex version for ROS2.

I want to tackle the following post migration ToDos:

• update default branch: from master to humble
• branch protection rule for humble
• update readmes (ROS2 readme (humble), ROS1 readme (master))
  • add logos for companies
  • add/update notice about and link to ROS1 and ROS2 branch
  • add news/announcements section, include info about which parts are migrated and which are not.

[Cakem1x]

Before changing the default branch to humble, I'd like to get confirmation from other maintainers on whether that will break anything critical (@spuetz @corot ).
The rationale for this change is that it makes the landing of new people on the repo's main page nicer, assuming most of them are interested in using ROS2.

[corot]

Before changing the default branch to humble, I'd like to get confirmation from other maintainers on whether that will break anything critical (@spuetz @corot ). The rationale for this change is that it makes the landing of new people on the repo's main page nicer, assuming most of them are interested in using ROS2.

I think the default branch should always be master. But if most new developments will be on ROS 2, it makes sense to

• rename master as noetic
• rename humble as master
  But as migration is still wip (costmap server missing), we need to wait to do that

Besides that, I think there are changes in jazzy that break compatibility with costmaps, so future master should work for jazzy, not humble