Add support for secrets from KV

[lonegunmanb]

Describe your changes

Issue number

Release pr for #55 and should fix #52.

Checklist before requesting a review

• The pr title can be used to describe what this pr did in CHANGELOG.md file
• I have executed pre-commit on my machine
• I have passed pr-check on my machine

Thanks for your cooperation!

[lonegunmanb]

This pr should be halt due to this requirement:

When using key_vault_secret_id, ignore_changes should be used to ignore any changes to value.

Now we haven't ignore value, and I don't think we have a way to customize ignore_changes list based on whether we've set key_vault_secret_id or not. I'd like to try azapi_update.

[DrizzlyOwl]

I did something similar here DFE-Digital/terraform-azurerm-container-apps-hosting#374

[lonegunmanb]

This pr should be halt due to this requirement:

When using key_vault_secret_id, ignore_changes should be used to ignore any changes to value.

Now we haven't ignore value, and I don't think we have a way to customize ignore_changes list based on whether we've set key_vault_secret_id or not. I'd like to try azapi_update.

After studied current implementation I'm pretty sure that the document is incorrect. I'm the author who contributed this feature to the provider, and I found that this notice in the document was added by the previous author of my pr (my pr was rebased on his pr), and I've improved the logic how we handle key_vault_secret_id and value (when key_vault_secret_id was set, value would be set empty by default in read), so we don't need to add value in ignore_changes list anymore.

I'll continue this pr.