chore: trigger npm publish on pr merge

[teebszet]

🔘 PR Type

• CI related changes
• Other... Please describe: build with node 18

📜 Background

Future work from here:
https://www.notion.so/xverseapp/Xverse-Core-Release-Instructions-0842d3b87f0142fbb27766e80f6b1401

🔄 Changes

• Yes, Incompatible API changes
• No, Adds functionality (backwards compatible)
• No, CI only

Changes:

• chore: refactored the workflows.
  • npm publish and github release publish are now triggered from merge of the release PR
  • no longer need the prerelease conditionals on the publish-gpr job
• chore: use node 18 for CI builds

Impact:

• ci only

✅ Review checklist

Please ensure the following are true before merging:

• Code Style is consistent with the project guidelines.
• Code is readable and well-commented.
• No unnecessary or debugging code has been added.
• Security considerations have been taken into account.
• The change has been manually tested and works as expected.
• Breaking changes and their impacts have been considered and documented.
• Code does not introduce new technical debt or issues.

[github-actions]

Test this PR with npm i --save-exact @secretkeylabs/xverse-core@5.2.0-ac391be

[victorkirov]

🚢