What does this PR do?

We found a bug in the libdatadog CI scripts related to config centralization. The CI job ran upon tagging a release with the current import URL has an hardcoded language value to nodejs.

I fixed it on the script and we need to import the new ones to have it correctly tagged.

⚠️ This will need to be cherry-picked into the ongoing release to avoid tagging golang keys are nodejs (with our tags, this would create a mess)

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• New code is free of linting errors. You can check this by running ./scripts/lint.sh locally.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!