fix(ci): constrain pygtrie for DVC

[tejo]

Description

Restore DVC dataset pulls after the pygtrie 2.6.0 release broke DVC 3.67.0 at runtime.

Changes Made

• Constrain pygtrie<2.6 inside the DVC pipx environment.
• Apply the constraint consistently to the reusable Go, JavaScript, and Python workflows.
• Keep DVC pinned at the existing 3.67.0 version.
• Normalize the Graphify workflow license header so the repository license check no longer attempts a forbidden bot update to a workflow file.

sqltrie 0.11.2, pulled transitively by DVC, accesses the private pygtrie.Trie._NONE_STEP attribute removed in pygtrie 2.6. Fresh CI runners therefore failed during dvc pull before application tests started.

Related Issues

N/A

Checklist

• I have used a PR title that is descriptive enough for a release note.
• I have tested these changes locally.
• I have added appropriate tests or updated existing tests.
• I have tested these changes on a cluster [name of the cluster] / customer [name of the customer].
• I have added appropriate documentation or updated existing documentation.