Fix CI and publish new package-lock.json artifact

The CI job fails with this error:

[16:48:35] I/launcher - Running 1 instances of WebDriver
[16:48:35] I/direct - Using ChromeDriver directly...
[16:48:35] E/runner - Unable to start a WebDriver session.
[16:48:35] E/launcher - Error: SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 88
Current browser version is 87.0.4280.66 with binary path /usr/bin/chromium
  (Driver info: chromedriver=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}),platform=Linux 4.15.0-47-generic x86_64)
    at Object.checkLegacyResponse (/home/gitlab-runner/builds/yoaLjpSZ/0/sed-paris/visiomanager/frontend/node_modules/selenium-webdriver/lib/error.js:546:15)
    at parseHttpResponse (/home/gitlab-runner/builds/yoaLjpSZ/0/sed-paris/visiomanager/frontend/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/home/gitlab-runner/builds/yoaLjpSZ/0/sed-paris/visiomanager/frontend/node_modules/selenium-webdriver/lib/http.js:441:30)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[16:48:35] E/launcher - Process exited with error code 100

Root cause:

• Chrome browser on CI VM has not the same version as chrome driver donwloaded by npm protractor package

Solution:

• Force protractor to download same version as chrome browser

Misc:

• publish package-lock.json as artifact to have trace of libraries version when pipeline pass