Task/one reg purpose only

[andrea-williams]

Changes made:

• Operation records allow a maximum of one registration_purpose, which is now an attribute on the Operation model
• the RegistrationPurpose model has been deleted (no longer necessary)
• all python unit tests have been updated for the new location of registration_purpose (232 unit tests were failing to begin with, it was a big refactor)
• edited front-end code so that the Registration Purpose field only expects one string, not an array of strings (there will be more work required for this form field, but I'll address that in my next PR for my actual ticket)
• updated Registration wiki to describe new registration purpose behaviour

[BCerki]

Nice work on this, it was huge! Some line notes in the PR, and one overall comment: The reg 1 tests shouldn't have needed updating because none of our changes at this point should affect reg 1 (unless we're doing custom migration stuff). I think the cause is adding registration_purpose into a v1 schema.

[ayeshmcg]

@andrea-williams
From the reporting perspective, the service looks good—currently, only one registration purpose is returned. However, one enhancement needs to be made in AdditionalReportingData.tsx.

Specifically, consider the following change:

  const registrationPurpose = (await getRegistrationPurpose(versionId))
    ?.registration_purpose;
  const includeElectricityGenerated =
    registrationPurpose === "OBPS Regulated Operation";

This will ensure that the includeElectricityGenerated property is determined correctly based on the registrationPurpose. Let me know if additional clarifications are needed.

[BCerki]

🤸