Set dags for document planning-application and title-boundary to run in DEV and STAGING

[tombrooks248]

There is some hardcoding which prevents the collections for

• document
• planning-application
• title-boundary

from showing in airflow, this is because they took a long time to run and this was a way of preventing them from running in prod and slowing everything down.

This ticket is about removing the hard coding, but also setting the availability to 'staging' so that they appear in DEV and STAGING but not in PRODUCTION and therfore do not slow anything down.

The availablity field was completed recently was done against this ticket - digital-land/config#2641 - if you want to read more detail about it.

[Ben-Hodgkiss]

As part of this ticket, let's rename availability to environment in the spec (and the references to it in the airflow-dags)

[tombrooks248]

OK so 3 PRs are now waiting and ready to go for the availability to environment

• fix: rename availability to environment airflow-dags#85
• fix: rename availability to environment specification#193
• fix: update availability to environment technical-documentation#439

To be implemented on Monday

[tombrooks248]

PR to set 3 dags to be staging and development only:

• feat: set 3 datasets to staging only specification#194

PR to remove the hard coding will follow on monday.

[tombrooks248]

Confirmed that the 3 dags (4 datasets) for title-boundary, planning application and document have been removed from Airflow PROD

Last step is to remove the hard coding which prevents these datasets from being run as part of the nightly run.