DB User Translation Layer & SDK migration

[josvazg]

Sample Translation layer for your consideration:

• The packages under internal/translation contain per Altas resource translation layers for users and deployments.

• Files in the controller package should not import the SDK library to call the API or use its types.

• All translations and upgrades are confined to the translation code.

• Contract tests would use the translation layer directly.

• This layout also enforces proper translations and comparisons, no more funky CMP or JSONCopies.

• See commit 142314606ac35d3d5d5568c1f6acccdf10c87bc8 for a version when the translation layer is on an atlas.go file within the same package using the old Go API client

• See commit 5d11f7cf28ca20b62e7e589356798a80fc4318de for the migration changes to the nee SDK alone.

Engineering Proposal: Translation Layer

All Submissions:

• [X] Have you signed our CLA?