guide the explorer to use the v7 of `cf`

[enkicoma]

by using v6 of cf you will face a none explanatory error: Staging through the v2 API is disabled https://github.com/cloudfoundry/cf-for-k8s/issues/540#issuecomment-773184268

Thanks for contributing to cf-for-k8s!

We've designed this PR template to speed up the PR review and merge process - please use it.

WHAT is this change about?

Please describe the change here The change is to guide the explorer to use v7 of cf or they will face an issue

Does this PR introduce a change to config/values.yml?

_Simply answer Yes or No. You can also review this "cf-for-k8s values for contributors" doc for up-to-date principles and guidelines for contributing values changes_ No

Acceptance Steps

Please replace this with a series of instructions (eg kubectl or cf cli commands) for how our Product Manager can verify that your changes were properly integrated.

Tag your pair, your PM, and/or team

Optional but it's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.

Things to remember

• Make sure this PR is based off the master branch
• Include any links to related PRs, issues, stories, slack discussions, etc... that will help establish context.
• Is there anything else of note that the reviewers should know about this change?
• Our CI uses concourse task files from HEAD of the develop branch. If your PR includes/requires CI changes, please ping the RelInt interrupt and they'll help apply the CI changes for you.
• Checkout the contributing guidelines

[linux-foundation-easycla[bot]]

• :x: - Valentin The commit (16093882b4420b2820f6c355830b2d4d79b08d61) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/176799169

The labels on this github issue will be updated when the story is started.

[cf-rel-int-status-bot]

Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:

[enkicoma]

will pull from dev instead of master