Bump pan-domain-node to v1.2.0

[LAKSHMIRPILLAI]

What does this change?

This PR is to bump pan-domain-node to v1.2
This is done to address the high severity vulnerability reported as FSBP S3.8 the bucket pan-domain-auth-settings should block public access here

This pull request bumps the pan-domain-node dependency to version 1.2.0 so that it reads the public key files by AWS SDK rather than unauthenticated direct HTTP request.

Changes are done in pan-domain-node library (guardian/pan-domain-node#47) to get the public key files with AWS SDK that requires AWS credentials in the execution environment.

How to test

Test in CODE (IN PROGRESS)

Steps

1. Deploy the branch to Editorial Tools::Editorial Collaboration

2. Open Composer CODE and load the page.

3. Enable Enable collaborative editing: this currently logs steps out to the console feature switch and reload the page

4. Check the Network tab to look for the POST requests to https://editorial-collaboration.code.dev-gutools.co.uk .We need to edit the body in order to trigger this

5. If it returns 200/201 or ok , it seems the changes are working

6. Also look for any error messages in the logs

[github-actions]

Deploy build 117 of Editorial Tools::Editorial Collaboration to CODE

All deployment options

• Deploy build 117 of Editorial Tools::Editorial Collaboration to CODE
• Deploy parts of build 117 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[waisingyiu]

It looks great, thank you @LAKSHMIRPILLAI .

Currently the CD has not been set up for PROD, but there is a PROD stack, presumably from one of the past commits of the main branch. So this PR will not be deployed to the PROD even after being merged. After we enable "block all public access" option in the panda S3 bucket, the PROD stack will probably stop working.

Having discussed with the team, we didn't think it was much of a concern because the editorial collaboration was not in production use at all.