### Apache Airflow version

2.7.1

### What happened

After upgrading to 2.7.1 from 2.5.3 we encountered those logs in the scheduler logs:

```[2023-09-11T05:52:34.865+0000] {logging_mixin.py:151} INFO - [2023-09-11T05:52:34.865+0000] {security.py:708} INFO - Not syncing DAG-level permissions for DAG 'DAG:<dag_name>' as access control is unset.```

Since we have multiple DAGs for the same DAG file (>40), and the DAG processor is running on a high period, we have a lot of redundant logs, which creates more unnecessary data to store.

Adding the setting `access_control={}` did not change the logs.

We don't want to manage the access control for each DAG, as we have a high-level approach, but we also don't want these logs.


### What you think should happen instead

Add some settings to allow avoid printing this info logs about sync permissions

### How to reproduce

Airflow Version - 2.7.1
Python - 3.11.5

Create a DAg without setting access_control and watch logs. e.g. `XXX/_data/scheduler/2023-09-11/dag_name.py.log`

### Operating System

Debian GNU/Linux 11 (bullseye)

### Versions of Apache Airflow Providers

_No response_

### Deployment

Docker-Compose

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit 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)

"""Returns a dict with a key of role name and value of role with early loaded permissions."""
        return {
            r.name: r
            for r in self.appbuilder.get_session.scalars(
                select(self.role_model).options(joinedload(self.role_model.permissions))
            ).unique()
        }
    def create_dag_specific_permissions(self) -> None:
        """
        Add permissions to all DAGs.
        Creates 'can_read', 'can_edit', and 'can_delete' permissions for all
        DAGs, along with any `access_control` permissions provided in them.
        This does iterate through ALL the DAGs, which can be slow. See `sync_perm_for_dag`
        if you only need to sync a single DAG.
        :return: None.
        """
        perms = self.get_all_permissions()
        dagbag = DagBag(read_dags_from_db=True)
        dagbag.collect_dags_from_db()
        dags = dagbag.dags.values()
        for dag in dags:
            root_dag_id = dag.parent_dag.dag_id if dag.parent_dag else dag.dag_id
            dag_resource_name = permissions.resource_name_for_dag(root_dag_id)
            for action_name in self.DAG_ACTIONS:
                if (action_name, dag_resource_name) not in perms:
                    self._merge_perm(action_name, dag_resource_name)
            if dag.access_control is not None:
                self.sync_perm_for_dag(dag_resource_name, dag.access_control)
    def update_admin_permission(self) -> None: