Add technical layer to handle change propositions (hexa, db storage, repositories,services etc)

[vincent-psarga]

• merge PR [EPIC] Propose modifications on a playbook artifact #115
• add playbookChangeManagement hexa
• "persist" data using Cache (use redis behind)
• add API endpoint to create Changeproposal

curl -X POST http://localhost:4200/organizations/<ORGA_ID>/changeProposals/ \
-H "Authorization: Bearer $PACKMIND_API_KEY_V3" \
-H "Content-Type: application/json" \
-d '{
  "type": "updateCommandName",
  "artefactId": "<RECIPE_ID>",
  "payload": {
    "oldValue": "<RECIPE_OLD_NAME>",
    "newValue": "<RECIPE_NEW_NAME>"
  },
  "captureMode": "commit"
}'

[cteyton]

Here:

export type CreateCommandChangeProposalCommand = PackmindCommand & {
  type: ChangeProposalType;
  artefactId: RecipeId;
  artefactVersion: number;
  payload: ScalarUpdatePayload;
  captureMode: ChangeProposalCaptureMode;
};

Should the "type" be limited to

type: ChangeProposalType.updateCommandName | ChangeProposalType.updateCommandDescription;

?

[cteyton]

Why do we have errors that use Object.setPrototypeOf(...)

Ex that does:

export class ChangeProposalNotFoundError extends Error {
  constructor(changeProposalId: ChangeProposalId) {
    super(`Change proposal with id "${changeProposalId}" was not found`);
    this.name = 'ChangeProposalNotFoundError';
    Object.setPrototypeOf(this, ChangeProposalNotFoundError.prototype);
  }
}

Ex that don't:

export class UnsupportedChangeProposalTypeError extends Error {
  constructor(type: ChangeProposalType) {
    super(`Unsupported change proposal type: ${type}`);
    this.name = 'UnsupportedChangeProposalTypeError';
  }
}

If unclear, we should set a packmind standard on this