Force GitHub Actions npm cache reset

[XDex]

Description

After merging #783, functional tests failed on main branch, due to npm cache not being reset after adding a new dev dependency.
This PR adds a mechanism for incrementing npm cache key value in GA workflows, so that it could be reset and functional tests would use the latest npm cache.
See this Cache Action issue for more context.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change which does not add functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.

[XDex]

@jonsnyder Could you please take a quick look?
Thanks!

[ninaceban]

Remove unnecessary spaces and add new lines at EOF where needed please.

[jonsnyder]

@shammowla can you take a look? You are more familiar with these workflow files.

[XDex]

Remove unnecessary spaces and add new lines at EOF where needed please.

@ninaceban Not sure what you mean, the redundant spaces have been already cleaned up and newlines already added at EOF automatically by Idea in my commit, you've probably mixed up the removed (red) and added (green) mods when reviewing..