include bootstrapExternalStatic* variables in doc

[manurodriguez]

Description

Starting in OCP 4.12 there are some variables that allow to statically assign IP/GW in the external net and DNS in 4.14. Also update bootstrapProvisioningIP references for 4.6.

Type of change

Please select the appropriate options:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This change is a documentation update

Testing

This is a change in the documentation.
The use of these variables is being tested in redhatci/ansible-collection-redhatci-ocp#426

Checklist

• I have performed a self-review of my own code
• If a change is adding a feature, it should require a change to the README.md and the review should catch this.
• If the change is a fix, it should have an issue. The review should make sure the comments state the issue (not just the number) and it should use the keywords that will close the issue on merge.
• A change should not be merged unless it passes CI or there is a comment/update saying what testing was passed.
• PRs should not be merged unless positively reviewed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign derekhiggins for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• ansible-ipi-install/OWNERS
• documentation/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @manurodriguez. Thanks for your PR.

I'm waiting for a openshift-kni member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.