### Apache Airflow version

2.7.0rc2

### What happened

In the Airflow UI, currently, the DAG Processor is visible in the Cluster Activity page even if there is no stand-alone dag processor. 

### What you think should happen instead

It should be hidden if there is no stand-alone dag processor.

### How to reproduce

Run Airflow 2.7 

### Operating System

Mac OS

### Versions of Apache Airflow Providers

Airflow > 2.7

### Deployment

Official Apache Airflow Helm Chart

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit PR?

- [X] 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)

"conn_type",
        "description",
        "host",
        "port",
        "is_encrypted",
        "is_extra_encrypted",
    ]
    
    
    
    _add_columns = _edit_columns = [
        "conn_id",
        "conn_type",
        "description",
        "host",
        "schema",
        "login",
        "password",
        "port",
        "extra",
    ]
    
    
    add_form = edit_form = ConnectionFormProxy
    add_template = "airflow/conn_create.html"
    edit_template = "airflow/conn_edit.html"
    add_widget = ConnectionFormWidget
    edit_widget = ConnectionFormWidget
    base_order = ("conn_id", "asc")
    def _iter_extra_field_names_and_sensitivity(self) -> Iterator[tuple[str, str, bool]]: