do not require that uuids in tracking IDs be version 4

[alaniwi]

This one-line commit will prevent esgdrs from making assumptions about what UUID version must be used in the tracking ID. Otherwise some valid data cannot be published.

I see that both clean and devel3 have had recent commits, and I am not sure which branch is relevant, so I have branched from where these two diverge from each other, so that it can be merged into either.

[alaniwi]

Example of a UUID string that failed the check when insisting on version 4:

83b5f0d6-10ed-11f0-a4b1-3cecef4e7350

This is version 1.

[ltroussellier]

nice catch,
but recent development will render this obselete.
the tracking_id will be validate through esgvoc :
i have just try it :

❯❯❯ uv run esgvoc valid hdl:21.14100/83b5f0d6-10ed-11f0-a4b1-3cecef4e7350 cmip6:tracking_id:
[True]

yes esgprep is under hot development right now