PC-1057: Implementing the Local Authority single source of truth

[Glenn-Clarke]

Link to Jira ticket

Description

• Updated information in line with the single source of truth document.
• Updated tests to reflect new information.
• Added comments to identify Legacy LAs which no longer exist/have been merged with others.

Checklist

• I have made any necessary updates to the documentation
• I have checked there are no unnecessary IDE warnings in this PR
• I have checked there are no unintentional line ending changes
• I have added tests where applicable
• If I have made any changes to the code, I have used the IDE auto-formatter on it
• If I have made any changes to website flow, I have checked forward and back behaviour is still consistent
• If I have made any changes to the Local Authority or Consortium data, I have made sure these changes have been reflected in the main HUG2 repository

[jdgage]

Could you add the new LA to populate_custodian_codes.sql please? We'll need to run that when we release

[jdgage]

Was this autoformatting?

[Glenn-Clarke]

Yes. It also put it like this:

HUG2
Public Website codebase

as well, but after I pulled the Public Website up a line, it let me keep it there, but would still revert to having the see tag broken up.

Should I leave it as it was originally, with all of the tag and its contents on one line?

[jdgage]

Not super bothered. Slight preference for how it was originally, but whatever auto-formatter thinks.

[Glenn-Clarke]

Added Worcestershire to the .sql

[samyou-softwire]

will the names in populate_custodian_codes.sql need to be updated too? as well as names in populate_consortium_codes.sql when that's merged

[jdgage]

will the names in populate_custodian_codes.sql need to be updated too? as well as names in populate_consortium_codes.sql when that's merged

Don't think it's worth the time

[Glenn-Clarke]

@jdgage I already had the solution just about done, and it exposed that we had lost a legacy LA along the way. (South Somerset) So I've pushed it now.