The gc-organisation list and the organisation db table can get out of sync

[smcmurtry]

Describe the bug

• As a @jimleroyer, when I run the notify api locally, I would like to have the organisations from this list populated in my local database so I can test the service creation/go live flows in a more realistic way.
• As a dev, I would like to keep the gc-organisations list consistent with the organisations database table in prod. This currently requires a manual process to be followed when a new organisation is added.

Bug Severity

See examples in the documentation

SEV-3 Minor

To Reproduce

Steps to reproduce the behavior:

1. run notification-api and notification-admin locally
2. Create a new service
3. Choose an organisation from the list
4. visit the service settings page
5. Observe that there is no organisation associated, since your local organisation table doesn't match what's in prod

Expected behavior

The organisation table should be populated using the gc-organisation list.

Impact

Impact on Notify team:
This can make it harder to test things locally.
There is also a risk that the gc-organisation list and the organisation table in prod will get out of sync over time.