### 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)

self.log.info(
                            "Revoking '%s' on DAG '%s' for role '%s'",
                            perm.action,
                            dag_resource_name,
                            role.name,
                        )
                        self.remove_permission_from_role(role, perm)
        resource = self.get_resource(dag_resource_name)
        if resource:
            _revoke_stale_permissions(resource)
        for rolename, action_names in access_control.items():
            role = self.find_role(rolename)
            if not role:
                raise AirflowException(
                    f"The access_control mapping for DAG '{dag_id}' includes a role named "
                    f"'{rolename}', but that role does not exist"
                )
            action_names = set(action_names)
            invalid_action_names = action_names - self.DAG_ACTIONS
            if invalid_action_names:
                raise AirflowException(
                    f"The access_control map for DAG '{dag_resource_name}' includes "
                    f"the following invalid permissions: {invalid_action_names}; "
                    f"The set of valid permissions is: {self.DAG_ACTIONS}"
                )
            for action_name in action_names:
                dag_perm = _get_or_create_dag_permission(action_name)
                if dag_perm:
                    self.add_permission_to_role(role, dag_perm)
    def create_perm_vm_for_all_dag(self) -> None: