feat: add fqdn parameter for r/csr

[spacegospod]

Summary of Pull Request

The resource for generating certificate signing requests accepts a resource type and automatically determines the correct FQDN for the request. This only works for resources of type VCENTER due to a limitation in the underlying API.

To resolve this we have to switch to an API andpoint that returns the full set of possible resources. Unfortunately in 5.1.1 this is not possible because this endpoint is not public.
A public endpoint will be available in an upcoming VCF release.

But even if we wait and try to fix this later we would encounter another problem. Some resources can have multiple instances (NSX for example). It would not be possible for the provider to determine which FQDN to use.

The only complete solution would be to explicitly provide the FQDN for the CSR as an input attribute of the resource.

Type of Pull Request

• This is a bug fix.
• This is an enhancement or feature.
• This is a code style/formatting update.
• This is a documentation update.
• This is a refactoring update.
• This is a chore update
• This is something else.
  Please describe:

Related to Existing Issues

Closes #195

Test and Documentation Coverage

I have added additional test cases for vcf_csr and vcf_certificate

For bug fixes or features:

• Tests have been completed.
• Documentation has been added/updated.

Breaking Changes?

• Yes, there are breaking changes.
• No, there are no breaking changes.

The identifiers for existing CSR resources will no longer be valid.
User's will have to regenerate their CSRs.

[tenthirtyam]

LGTM.

I've added the breaking-change label to the pull request so let's be sure to make this a minor release vs patch - 0.10.0 - and include a Breaking Change section at the top of the CHANGELOG.md on release.