Properly urlescape password in tests hook and Jenkins pipeline

[eiri]

Checklist

• Tick to sign-off your agreement to the Developer Certificate of Origin (DCO) 1.1
• Added tests for code changes or test/build only changes
• Updated the change log file (CHANGES.md|CHANGELOG.md) or test/build only changes
• Completed the PR template below:

Description

This PR properly encodes password in Jenkins pipeline as required by our own README and decodes it in test's hook, since node's new URL doesn't do that. This solves an issue with test password that might contain URL components.

Also this PR bumps eslint and eslint-config-standard to unlock its cross deps, that break npm ci

Approach

Schema & API Changes

Security and Privacy

Testing

Monitoring and Logging

[vmatyus]

since node's new URL doesn't do that.

The opposite, is true new URL does encoding in hook.js.
But as I see the DB comparison fails even after password decoding.
Might this is the problem, an encoded url should be stored in env var to be a match with the backed-up DB.

Here is a small node snippet:

> url = "http://user:p@ss@localhost"
'http://user:p@ss@localhost'
> new URL(url)
URL {
  href: 'http://user:p%40ss@localhost/',
  origin: 'http://localhost',
  protocol: 'http:',
  username: 'user',
  password: 'p%40ss',
  host: 'localhost',
  hostname: 'localhost',
  port: '',
  pathname: '/',
  search: '',
  searchParams: URLSearchParams {},
  hash: ''
}

[eiri]

@vmatyusGitHub yes, this is exactly what I said, node's doesn't do decoding of urlencoded password, so this need to be done in hook