[CT-3332] Remove usage of dbt.semver in dbt/adapters

[MichelleArk]

Housekeeping

• I am a maintainer of dbt-core

Short description

dbt.semver.VersionSpecifier.from_version_string and dbt.semver.VersionSpecifier.to_version_string

are used in the AdapterContainer to fire an event when registering adapters.

Implementation options:

1. semver module could be moved to new dbt/common directory, created in Feature/decouple adapters from core #8906
2. adapter registration can be moved into core ([CT-3335] Move adapter registration (factory) to core #9025)
3. functionality of VersionSpecifier.from_version_string and VersionSpecifier.to_version_string could be re-implemented in a standalone adapter version method defined in dbt/adapters
   • could use semantic-version package, which is used by dbt-core-bundles: https://github.com/dbt-labs/dbt-core-bundles/blob/main/requirements.txt#L3

(3) feels most practical given the limited amount of functionality from semver used in dbt/adapters.

Acceptance criteria

dbt/adapters has no dependency on dbt.semver

Impact to Other Teams

1p adapter imports will need to be updated, but those can be done separately as part of a bundled migration of 1p for #8917 if the work is done on a feature branch: #8906

Will backports be required?

No

Context

No response

[VersusFacit]

Progress

direct dbt semver imports in adapters and references to VersionSpecifier

• Redshift
• Snowflake
• Bigquery
• Spark
• Postgres

[VersusFacit]

Update. Waiting for some answers from Cloud config folks on safety to address this with a simple move. I have the code change for Core pretty much good to go. Just don't want to merge before I have a plan for downstream workflows.

[MichelleArk]

Resolved by: #9166