Requesting to invert chessboard_x-chessboard_x and chessboard_x composer names

I've been working on the drupal/chessboard 8.x-2.x branch and had released 8.x-2.0-unstable3. Recently I found some time, I finally decided to bite the bullet and moved all submodules into their own drupal projects. (Currently 1.0.x branches). I also created a chessboard 3.0.x branch and removed the submodules from that branch. (I also released 8.x-2.0-alpha1 which now resolves unlike the unstable releases)

So now I would like to make dependencies work for the new projects and so I'm requesting to swap namespaces/ composer packages names for the "submodules". So for example drupal/chessboard_lib would then map to the chessboard_lib project instead of to the chessboard project. (Now I need to require drupal/chessboard_lib-chessboard_lib). (And then for the chessboard project 2.x submodule you would need to require drupal/chessboard-chessboard_lib which is totally fine. Nobody is using that. I'm still going to maintain an identical branch though.)

1. chessboard_lib:chessboard_lib vs chessboard:chessboard_lib
2. chessboard_field:chessboard_field vs chessboard:chessboard_field
3. chessboard_filter:chessboard_filter vs chessboard:chessboard_filter
4. chessboard_images:chessboard_images vs chessboard:chessboard_images
5. chessboard_images_formatter:chessboard_images_formatter vs chessboard:chessboard_images_formatter
6. chessboard_plain_text_formatter:chessboard_plain_text_formatter vs chessboard:chessboard_plain_text_formatter

Even though I'm pretty sure that no drupal.org project has a dependency on one of my dev-2.x chessboard submodules I still plan to create 2.0.x branches (and releases) for these new Drupal projects that will have code identical to their corresponding 8.x-2.x submodule, so swapping the namespaces should have no impact with proper dependency management.

Thanks a lot!