[FLINK-24940] [docs] correct usage about how to create Hive catalog via Flink SQL CLI

[luoyuxia]

What is the purpose of the change

• As it's not supported to use yaml in SQL CLI, the documatation about how to create hive catalog in SQL CLI is out of date.
  The pr is to correct the usage.

Brief change log

• modify the hive_catalog.md

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive):no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no

[flinkbot]

CI report:

• bb1b65c Azure: SUCCESS
• 5e24fd6 Azure: PENDING

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit eec199b (Thu Nov 18 12:25:47 UTC 2021)

Warnings:

• This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

Details

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[MartijnVisser]

Thanks a lot for the PR. It would be great if you could also remove the other mentions of the version number.

[MartijnVisser]

@AHeise Please merge

[luoyuxia]

@MartijnVisser Could you please help merge it ?

[MartijnVisser]

@luoyuxia Yes, let me rebase and squash commits to verify that it will still work and then I'll merge it. Apologies for the delay!

[MartijnVisser]

Build passed in https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=34343&view=results