Disable issues and enable discussions for Python Client

The client is pretty much entirely generated from the main airflow
repo now - so any fixes should be implemented there. So it makes
sense that all issues should be created and fixed there.

Issues opened here are generally stale and they were terribly outdated
so instead of trying to keep issues here I propose to just have
discussions opened in the client, and if any of those discusssions
will result in a proposal we will ask those who discuss it here to
open an issue or PR in the main repo.

Author: potiuk

.asf.yaml

@@ -26,9 +26,11 @@ github:
     - python
   features:
     # Enable issues management
-    issues: true
+    issues: false
     # Enable projects for project management boards
     projects: false
+    # Enable discussions
+    discussions: true
   enabled_merge_buttons:
     squash: true
     merge: false

README.md

@@ -19,6 +19,17 @@
 
 # Apache Airflow Python Client
 
+> [!NOTE]
+> Code in this repository is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech)
+> project using Open-API specification from the Apache Airflow repository. The process of generating the code is
+> described in [Python Client Readme](https://github.com/apache/airflow/blob/main/clients/README.md).
+> We enabled [GitHub discussions](https://github.com/apache/airflow-client-python/discussions)
+> in the `airflow-client-python` repository, and we encourage you to start discussions if you have any questions
+> or suggestions to improve the client. However, in case the discussions result in a need to create an
+> actionable issuee, the issues in this repo are not enabled. Instead, you should create GitHub issues or
+> even PRs improving those in the main [Apache Airflow repository](https://github.com/apache/airflow).
+
+
 # Overview
 
 To facilitate management, Apache Airflow supports a range of REST API endpoints across its
@@ -33,6 +44,7 @@ Content-type: application/json
 Accept: application/json
 ```
 
+
 ## Resources
 
 The term `resource` refers to a single type of object in the Airflow metadata. An API is broken up by its