Update pki_secret_backend_crl_config to be more resilent to unknown response fields

[stevendpclark]

Description

Do not pass in the PKI CRL configuration response map directly into util.SetResourceData as this will fail if an unknown field is returned from Vault that isn't listed in the resource's schema. We encountered this within the Vault 1.19 release where the resource broke when max_crl_entries was added.

│ Error: error setting resource data for key "max_crl_entries", err=Invalid address to set: []string{"max_crl_entries"}
│
│   with vault_pki_secret_backend_crl_config.crl_config,
│   on main.tf line 8, in resource "vault_pki_secret_backend_crl_config" "crl_config":
│    8: resource "vault_pki_secret_backend_crl_config" "crl_config" {

Also this includes a slight refactoring to update the methods to the non-deprecated values along with removing duplication by adding a common method that builds up the list of fields based on Vault version.

Checklist

• Added CHANGELOG entry (only for user-facing changes)
• Acceptance tests where run against all supported Vault Versions

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

[stevendpclark]

This is the main fix here, passing in config.Data into util.SetResourceData was causing issues when the Data map contained an unknown field