Add resources for uuid v4 and v7

[masongup-mdsol]

Related Issue

Fixes #402
Fixes #511

Description

The UUIDs generated by the existing random_uuid resource are not valid UUIDs per RFC 4122, so they cause problems when a user attempts to use them in a system which expects UUIDs to be a specific version. Per the discussion on #402, I have done this by cloning the existing uuid resource, renaming it as uuid4 and uuid7 respectively, and using the Google Go UUID library instead with the appropriate methods to generate valid UUIDs of the appropriate versions. This way, users of the existing uuid resource will continue to have the same behavior without making any changes. Users who need one of these UUID versions can use the specific resource for that so that it is clear to any readers of the code what version is being used and that that version is being used intentionally.

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Given that this is random data, there are no security controls involved.

[hashicorp-cla-app]

All committers have signed the CLA.

[rainkwan]

Hi @masongup-mdsol,

I can review this after signing the CLA. 👍🏽

[masongup-mdsol]

Ah okay, I thought I had signed it already, but I guess I didn't finish the workflow properly before. I think it should be good now.

[rainkwan]

Hi @masongup-mdsol thank you for your contribution! 😄

This looks pretty reasonable, I wanted to ask if you could create a changelog entry for this as an enhancement. And also if you can run make generate so that the CI passes.

Thank you!

[masongup-mdsol]

Thanks @rainkwan, I have done both

[chrisjaimon2012]

any timeline regarding when this can be released?

[rainkwan]

Everything seems reasonable to me