fix(oracle-database): use PATCH instead of PUT for autonomous-database update

[Copilot]

az oracle-database autonomous-database update was issuing a PUT (create-or-replace) request instead of PATCH, causing the Oracle Database API to treat it as a new create call and return (400) Provisioning failed. A database with the same name exists.

Changes

• _update.py: Changed AutonomousDatabasesCreateOrUpdate.method from "PUT" to "PATCH" so the update command sends only the modified fields
• _update.py: Removed 201 from accepted response status codes — PATCH returns 200/202, never 201

Related command

az oracle-database autonomous-database update

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi Copilot,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[Yong Zhang (yonzhan)]

oracle-database