### Description

https://github.com/apache/airflow/pull/17946 implements a `/robots.txt` endpoint to block search engines crawling Airflow - in the cases where it is (accidentally) exposed to the public Internet.

If we record any GET requests to that end-point we'd have a strong warning flag that the deployment is exposed, and could issue a warning in the UI, or even enable some kill-switch on the deployment. 

Some deployments are likely intentionally available and rely on auth mechanisms on the `login` endpoint, so there should be a config option to suppress the warnings.

An alternative approach would be to monitor for requests from specific user-agents used by crawlers for the same reasons

### Use case/motivation

People who accidentally expose airflow have a slightly higher chance of realising they've done so and tighten their security.

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

airflow/www/views.py
priority = [
            'failed',
            'upstream_failed',
            'up_for_retry',
            'up_for_reschedule',
            'queued',
            'scheduled',
            'deferred',
            'sensing',
            'running',
            'shutdown',
            'restarting',
            'removed',
            'no_status',
            'success',
            'skipped',
        ]
        child_instances = [child['instances'] for child in children if 'instances' in child]
        child_instances = [item for sublist in child_instances for item in sublist]
        children_start_dates = [
            item['start_date'] for item in child_instances if item['run_id'] == dag_run.run_id