RUM-6120 Upgrade Github action to run on Node.js 20

[mariedm]

This PR updates the repository to use Node.js 20 in alignement with GitHub’s recent transition to Node.js 16 for GitHub Actions.

Given that we were already using Node.js 18 in the dependencies, and that Github Action doesn't support Node.js 18, it made sense to move directly to Node.js 20.

[datadog-datadog-prod-us1]

🔴 Code Quality Violation

Suggested change

	const setFailedMock = jest.spyOn(core, 'setFailed').mockImplementation(() => {})
	const setFailedMock = jest.spyOn(core, 'setFailed').mockImplementation(() => {/* empty */})

Empty statement. (...read more)

Empty or non-functional blocks in the code can be misleading and lead to maintenance difficulties. They can also lead to a false sense of security or functionality. While they may not directly introduce security issues, their presence can suggest that some logic or error handling is implemented when it is not.

    

[maxep]

/nit This suggestion is better than a console call IMHO

[datadog-datadog-prod-us1]

🟠 Code Quality Violation

Unexpected console statement. (...read more)

Debugging with console is not considered a bad practice, but it's easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.

    

[datadog-datadog-prod-us1]

🟠 Code Quality Violation

Unexpected console statement. (...read more)

Debugging with console is not considered a bad practice, but it's easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.

    

[datadog-datadog-prod-us1]

🟠 Code Quality Violation

Unexpected console statement. (...read more)

Debugging with console is not considered a bad practice, but it's easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.