### Apache Airflow version

2.5.1

### What happened

/calendar page give a problem, here is the capture



![屏幕截图 2023-01-30 093116](https://user-images.githubusercontent.com/19165258/215369479-9fc7de5c-f190-460c-9cf7-9ab27d8ac355.png)


### What you think should happen instead

_No response_

### How to reproduce

_No response_

### Operating System

Ubuntu 22.04.1 LTS

### Versions of Apache Airflow Providers

Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

### Deployment

Other

### Deployment details


Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

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

"""
    Adds `.can_edit`, `.can_trigger`, and `.can_delete` properties
    to DAG based on current user's permissions.
    Located in `views.py` rather than the DAG model to keep
    permissions logic out of the Airflow core.
    """
    if "dag" in context:
        dag = context["dag"]
        can_create_dag_run = get_airflow_app().appbuilder.sm.has_access(
            permissions.ACTION_CAN_CREATE, permissions.RESOURCE_DAG_RUN
        )
        dag.can_edit = get_airflow_app().appbuilder.sm.can_edit_dag(dag.dag_id)
        dag.can_trigger = dag.can_edit and can_create_dag_run
        dag.can_delete = get_airflow_app().appbuilder.sm.can_delete_dag(dag.dag_id)
        context["dag"] = dag
before_render_template.connect(add_user_permissions_to_dag)