[Confluent] UX improvement

[fengzhou-msft]

• [BREAKING CHANGE] az confluent organization create: Remove --user-detail, the parameter is now auto-filled by the email address, first name and last name decoded from access token.
• [BREAKING CHANGE] az confluent organization create: Flatten --offer-detail to --offer-id, --plan-id, --plan-name, --publisher-id and --term-unit.
• Add new command az confluent offer-detail show.
• az confluent organization create: Add Owner or Contributor access check of the subscription before creating the organization.
• az confluent organization delete: Customize confirmation message based on plan type.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

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?

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[yonzhan]

Confluent