Merge jnosql-communication-driver and jnosql-mapping-extension repositories into a single module[Task]

[otaviojava]

The task for the: #353

Structure

• Rename the project from jnosql-communication-driver to jnosql-databases
• Rename the project from jnosql-mapping-extension to jnosql-extensions
• Update Parent-pom to use org.eclipse.jnosql.databases as group ID
• Create and define tags to test that needs a database and disable it by default.

Merge project

This one needs to merge communication and mapping into a single module.

• We need to be sure that we won't impact the package name
• Update documentation at readme
• Remove codes from the extension repository

Databases

• jnosql-arangodb-extension
• jnosql-cassandra-extension
• jnosql-couchbase-extension
• jnosql-elasticsearch-extension
• jnosql-hazelcast-extension
• jnosql-mongodb-extension
• jnosql-orientdb-extension
• jnosql-solr-extension

[otaviojava]

I've created this issue to rename the project:

• https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2894
• https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2895

[otaviojava]

@dearrudam let me know if you wanna take some of this.

[dearrudam]

@otaviojava, I could work at this one: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2894, but I think that I need to have permission to do it. Could you help me with that?!

[dearrudam]

@otaviojava never mind! This renaming process could be done later...

I could work on the jnosql-arangodb-extension, okay?

I got an idea: I think that you could convert each item of this "Databases" list into sub-issues. With that, any of us could assign ourselves to one of these sub-issues. Also, on each state changing of each sub-issue will be propagated to this issue automatically.

[otaviojava]

I like it; I'll take the Cassandra one to feel the terrain.

[otaviojava]

the ulrs have been updated:

• https://github.com/eclipse/jnosql-databases
• https://github.com/eclipse/jnosql-extensions

[otaviojava]

I'll close this one.
Thank you @dearrudam