chore: Dependencies update for Zowe 2.14

[pj892031]

Description

This PR upgrades dependencies before releasing Zowe 2.14 (Java + NPM for UI)

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[achmelo]

Looks good. I am only not sure why there are changes in tests. Are they relevant to dependency updates?

[pablocarle]

Looks good. I am only not sure why there are changes in tests. Are they relevant to dependency updates?

Some tests were failing, especially the ones in cloud gateway about the parsing of cookies, perhaps with the upgrade the return value changed, i.e. now the getCookies method would return something like "Cookie1=value1; Cookie2=value2" and the logic there did not allow for the correct parsing of this string.