{hpc-cache} breadth coverage for hpc cache

[qianwens]

---

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]

add to S167

[haroldrandom]

needs statement of code owner in .github/CODEOWNER.

[rebecca-makar]

@qianwens I am member of HPC Cache team, this is missing Flush and Upgrade for Cache. Still testing other commands but those two are needed.

[qianwens]

@qianwens I am member of HPC Cache team, this is missing Flush and Upgrade for Cache. Still testing other commands but those two are needed.

I will add these support in another PR.

[haroldrandom]

file name src/hpc-cache/azext_hpc_cache/tests/latest/test_hpc-cache_scenario.py is a convention,
should be test_hpc_cache_scenario.py

[qianwens]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[qianwens]

@qianwens I am member of HPC Cache team, this is missing Flush and Upgrade for Cache. Still testing other commands but those two are needed.

I will add these support in another PR.

I have added flush and upgrade in this PR