Add workflow to build a deploy artifact and deploy to GH pages

[amcaplan]

WHY are these changes introduced?

Making the Version Packages PR just about versioning packages, instead of being 99.99% static docsite updates every time.

WHAT is this pull request doing?

Sets up a GitHub action that should generate and push our API docs to GitHub pages

How to test your changes?

We'll have to merge and see!

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.33% (+0.01% 🔼)	8892/11804
🟡	Branches	70.57% (+0.03% 🔼)	4324/6127
🟡	Functions	75.1%	2337/3112
🟡	Lines	75.87% (+0.02% 🔼)	8404/11077

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / app-event-watcher.ts	93.83% (-1.23% 🔻)	86.49%	90.48%	98.61%

Test suite run success

2001 tests passing in 904 suites.

Report generated by 🧪jest coverage report action from b7083d2

[isaacroldan]

Just to confirm, this job will only be executed when a PR is merged right? never on an open PR or non-main branch?
(because if it does, anyone could publish anything to our pages 😅 )

[gonzaloriestra]

@isaacroldan yes, it will only happen when merging to main.

But I'm not getting this:

• You are uploading docs to GH pages, but where exactly and why? Were we doing that?
• If we don't merge the generated docs or create a PR, they will keep appearing in the Version Packages PR, no?