Rename common package to common

[benmoriceau]

What

In order to make a package to match its module name, it is renamed.

[github-actions]

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

• source-clickhouse-strict-encrypt
• destination-rockset
• source-oracle
• source-kafka
• destination-bigquery
• source-alloydb
• source-snowflake
• source-scaffold-java-jdbc
• source-mssql-strict-encrypt
• destination-kinesis
• destination-jdbc
• destination-mssql-strict-encrypt
• destination-snowflake
• destination-e2e-test
• source-cockroachdb
• destination-oracle-strict-encrypt
• destination-bigquery-denormalized
• destination-pulsar
• source-mysql
• destination-tidb
• source-db2-strict-encrypt
• source-e2e-test-cloud
• source-clickhouse
• destination-mongodb-strict-encrypt
• source-sftp
• destination-postgres
• source-mysql-strict-encrypt
• destination-elasticsearch-strict-encrypt
• destination-mongodb
• destination-meilisearch
• destination-mariadb-columnstore
• destination-gcs
• source-elasticsearch
• destination-postgres-strict-encrypt
• destination-dev-null
• destination-elasticsearch
• destination-local-json
• source-mongodb-strict-encrypt
• destination-clickhouse
• destination-keen
• source-db2
• destination-redis
• destination-azure-blob-storage
• source-cockroachdb-strict-encrypt
• destination-pubsub
• source-postgres
• destination-databricks
• destination-redshift
• source-postgres-strict-encrypt
• destination-mysql
• source-tidb
• destination-csv
• source-oracle-strict-encrypt
• destination-r2
• destination-scylla
• destination-dynamodb
• destination-cassandra
• destination-mssql
• destination-kafka
• source-e2e-test
• destination-aws-datalake
• destination-oracle
• destination-mqtt
• destination-mysql-strict-encrypt
• source-alloydb-strict-encrypt
• source-jdbc
• source-redshift
• source-mssql
• destination-clickhouse-strict-encrypt
• destination-s3
• source-mongodb-v2
• source-bigquery