Versioning and naming

[frantuma]

In scope of #8395, and similar to what applied to swagger-core in swagger-api/swagger-core#2485, this ticket is about renaming projects, maven artifacts, and packages of swagger-codegen and swagger-codegen-generators projects and modules.

The immediate goal is adopting a naming and versioning policy allowing v2 and v3 libraries to coexist; the update will also ensure a consistent version upgrade mechanism, avoiding (transitive) dependencies issues for as much as possible.

It includes the following changes:

• Rename groupdId of root of both projects to io.swagger.codegen.v3
• Rename groupdId of swagger-codegen module to io.swagger.codegen.v3
• Rename groupdId of swagger-codegen-cli module to io.swagger.codegen.v3
• Rename groupdId of swagger-codegen-maven-plugin module to io.swagger.codegen.v3
• Rename groupdId of swagger-generator module to io.swagger.codegen.v3
• Rename groupdId of swagger-codegen-generators module to io.swagger.codegen.v3

---

• Rename root package of swagger-codegen module to io.swagger.codegen.v3
• Rename root package of swagger-codegen-cli module to io.swagger.codegen.v3.cli
• Rename root package of swagger-codegen-maven-plugin module to io.swagger.codegen.v3.maven
• Rename root package of swagger-generator module to io.swagger.codegen.v3.generator
• Rename root package of swagger-codegen-generators module to io.swagger.codegen.v3.generators

---

• Adapt POM, all CIs config files and any affected config/metadata

[frantuma]

implemented in #8451 and related