feat: Validate UUID without creating new UUID

[ljahier]

Overview

This pull request introduces a new function, Validate(s string) error, in response to the request in issue #137. The primary goal is to provide a way to validate UUID strings without the overhead of creating a UUID object and its underlying byte array, as currently happens in the Parse(s string) (UUID, error) function.

Changes Made

• Implemented Validate(s string) error which checks the format of the UUID string without generating a UUID object.
• Added unit tests to ensure the correctness of the validation logic, particularly for edge cases and various UUID string formats.

Rationale

This change is particularly useful in scenarios where UUIDs are frequently validated but not used in their byte form. It optimizes performance by eliminating unnecessary memory allocations associated with UUID object creation, especially in high-throughput environments.

Testing

Unit tests have been added to cover various cases:

• Standard UUID formats (with and without hyphens)
• UUIDs with the "urn:uuid:" prefix
• Braced UUID strings
• Edge cases with invalid UUID strings

The tests ensure that the new validation function behaves as expected across a wide range of valid and invalid inputs.

Impact

This update introduces a non-breaking change, adding new functionality to the library without altering existing behaviors.

Looking forward to your feedback and suggestions on this implementation!

Resolves #137

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.