Force new resource on database collation update.

[ShepardToTheStars]

Bug fix for Issue #844.

• Acceptance test coverage of new behavior. (See question below)
• Documentation updates
• Well-formed Code

Are acceptance tests needed for this change? (It doesn't look like the other SQL database resources are testing for this specific condition either)

[mbfrahry]

Hey @vlouwagie, it's always good to write a quick test to confirm that it works as expected and just in case anything changes with the api or sdk. I've written one and can push it up to this branch if that's ok with you. Otherwise this looks good!

[ShepardToTheStars]

@mbfrahry Sounds good to me. Thank you for doing that. 😄

[mbfrahry]

Not a problem. I've submitted a new PR since I can't commit to this one. Your commits are saved in that branch so I'll close this in favor of #1066. Thanks again for this submission!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!