[PM-6271] Propose cipher versioning with migration in data layer

[coroiu]

Type of change

- [ ] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

This PR contains a proof of concept for the "Data layer" approach described here: https://bitwarden.atlassian.net/wiki/spaces/~62955327d9eae9006f348ae9/pages/944701442/Proof+of+concept+Cipher+versioning#Data-%E2%80%9Clayer%E2%80%9D

Code changes

The PR contains a lot of changes, but most are either import path changes or duplicate boilerplate code.
The important parts are:

API Layer

• libs/common/src/vault/models/ciphers/api/v1 & v2: These folders contain the representation of the different
  versions of ciphers in the api layer. These are used by both responses and requests
• libs/common/src/vault/models/ciphers/response/v1 & v2: These folders contain the representation of the different versions of ciphers in the api layer
• libs/common/src/vault/models/ciphers/response/version-agnostic: This contains a wrapper on top of v1/v2 to allow the rest of the codebase to handle responses without necessarily knowing which version it has.

Data Layer

• libs/common/src/vault/models/ciphers/data/v1 & v2: These folders contain the representation of the different
  versions of ciphers in the data layer.
• libs/common/src/vault/models/ciphers/response/version-agnostic: This contains a wrapper on top of v1/v2 to allow the rest of the codebase to handle data classes without necessarily knowing which version it has. This class is also responsible for migration between versions.

Cipher Service

• libs/common/src/vault/services/cipher.service.ts Updated to support migration

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team
• Ensure that all UI additions follow WCAG AA requirements

[github-actions]

Checkmarx One – Scan Summary & Details – 5a37619c-74ce-417f-ab7e-fcdd7c00abb9

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 481	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 473	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 457	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 465	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Fixed Issues

Severity	Issue	Source File / Package
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 496
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 488
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 480
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 504