Allow PATCH role endpoint to remove permissions not included in PATCH call

[tseruga]

closes: #25734

Rationale:
PATCH /api/v1/roles/[role] previously would only ever append permissions to a role, never removing permissions that were omitted from the PATCH call. This makes it impossible to programmatically remove permissions from a role via the API.

Change:
This change changes the behavior of the PATCH api for roles to allow for both adding and removing permissions based on which permissions are passed via the PATCH call.

Permissions omitted from the API call are removed from the role. Permissions passed via the API call are added to the role.

Notes:
This technically could be considered a breaking change. The way the PATCH endpoint is currently implemented is not how it should work (based on how PATCH endpoints generally work) but users could have built their systems using this awkward behavior.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https:/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[potiuk]

Sorry for long no response.

I think this is not the right approach I believe. What currently the PR implements is really "PUT" semantics, not "PATCH". What PATCH should do is to be able to specifically say "ADD" / "DELETE" instead of replacing the whole content. So there should be (ideally backwards compatible) way of applying PATCH.

I think a good way explaining it, and possible approach is here (with explanation why the approach is PUT disguised in PATCH:

https://medium.com/@isuru89/a-better-way-to-implement-http-patch-operation-in-rest-apis-721396ac82bf

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.