Update mailing list information in DOAP
diff --git a/doap_airflow.rdf b/doap_airflow.rdf
index 5e7c4984af6a7..872e7d7196f48 100644
--- a/doap_airflow.rdf
+++ b/doap_airflow.rdf
@@ -33,7 +33,7 @@ related to workflow automation and scheduling that can be used to author and
 manage data pipelines.
 </description>
     <bug-database rdf:resource="https://github.com/apache/airflow/issues" />
-    <mailing-list rdf:resource="https://lists.apache.org/list.html?dev@airflow.apache.org" />
+    <mailing-list rdf:resource="dev@airflow.apache.org" />
     <download-page rdf:resource="https://airflow.apache.org/docs/apache-airflow/stable/installation/index.html" />
     <programming-language>Python</programming-language>
     <programming-language>JavaScript</programming-language>

The mailing list link in DOAP is rendered as "mailto:" link at the https://projects.apache.org/project.html?airflow page so we should change it to regular email address.

<!--
 Licensed to the Apache Software Foundation (ASF) under one
 or more contributor license agreements.  See the NOTICE file
 distributed with this work for additional information
 regarding copyright ownership.  The ASF licenses this file
 to you under the Apache License, Version 2.0 (the
 "License"); you may not use this file except in compliance
 with the License.  You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing,
 software distributed under the License is distributed on an
 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
 under the License.
 -->

<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.

Feel free to ping committers for the review!

In case of an existing issue, reference it using one of the following:

closes: #ISSUE
related: #ISSUE

How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->



<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information.
In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
