build(docs-infra): introduce new process for generating data for the events page

[gkalpak]

This PR introduces a new process for generating data for the AIO events page, which streamlines the process and minimizes duplication and manual work. For more details, see aio/scripts/generate-events/README.md.

TODECIDE

• How we want to present dates (esp. the Starts on prefix).
  We will use the YYYY-MM-DD format and change the column header to "Start date"
• What to do about events with invalid dates. (Currently, the script prints them and then removes them from the list.)
  The current behavior is fine.
• Whether we want to update past events with links (or maybe just the 2022 ones).
  We can do that, but we also don’t have links for all the events. We’ll try to be mindful for 2022 events from now on. It’s fine if we don’t have links for all the events from the start.
• Whether we want to automatically keep X last years worth of events.
  (We could keep them all in the DB, but not put them in events.json for displaying in AIO.)
  For now, we will display all events (since 2019). In the future, we might want to revisit this and only show a limited number of years or show all available years but as collapsibles.
• How much back we want to go. (NOTE: Sheets before 2019 use different formats).
  We’re good until 2019.
• Whether to only retrieve events from the DB when building next.angular.io on upstream CI and get next.angular.io/generated.events.json for other builds.
  (This would allow us to lock down reading on the database fwiw.)
  We'll go with the current implementation for simplicity. We can revisit in the future if the number of reads becomes problematic.

TODO

• Set up Apps Script extension on the actual spreadsheet and create time-driven trigger.
• Ensure the installable trigger creator has access to the angular-io Firebase project.
• Update DB_URL value in constants.js and index.mjs.
• Rework some parts of the implementation - see here.
  PR: feat(github-actions): implement GitHub Action for creating a PR from local changes dev-infra#738
• List specific ways to get in touch with DevRel in aio/content/marketing/events-contributing.md.
• Link to the GitHub Action that periodically updates events in aio/scripts/generate-events/README.md.
• Address TODOs in .github/workflows/update-events.yml.
• Update payload sizes in aio-payloads.json.

[mary-poppins]

You can preview 6ca41c3 at https://pr45588-6ca41c3.ngbuilds.io/.

[mary-poppins]

You can preview 832adb0 at https://pr45588-832adb0.ngbuilds.io/.

[mary-poppins]

You can preview a551b54 at https://pr45588-a551b54.ngbuilds.io/.

[mgechev]

Left two comments. Looks really well!

[jessicajaniuk]

reviewed-for: size-tracking

[mary-poppins]

You can preview ed461dc at https://pr45588-ed461dc.ngbuilds.io/.

[mary-poppins]

You can preview fcce55c at https://pr45588-fcce55c.ngbuilds.io/.

[mary-poppins]

You can preview c4cb9f7 at https://pr45588-c4cb9f7.ngbuilds.io/.

[mary-poppins]

You can preview 8573647 at https://pr45588-8573647.ngbuilds.io/.

[mary-poppins]

You can preview 9ec7d45 at https://pr45588-9ec7d45.ngbuilds.io/.

[AndrewKushnir]

Merge-assistance: needs a "green light" from @mgechev before landing this PR.

[AndrewKushnir]

Got a "green light" from @mgechev offline, so we can proceed with merging this PR. // cc @dylhunn

[dylhunn]

This PR was merged into the repository by commit c9241fd.

[dylhunn]

@gkalpak Was this PR related to update-events.yml? I have started getting emails that the Update AIO events script has failed to run, with links like this one.

[gkalpak]

Yes. As discussed "offline", notifications for scheduled workflows go to the last person that modified the schedule: GitHub docs

Once the errors are fixed, hopefully there won't be any notifications 😁

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}