Separate webpage build from data processing steps in action

[LukasWallrich]

We are now doing a lot of data processing in the build action

• Tenzing
• Curated Resources
• Google Analytics
• References (to come)

It is not necessary to do all of that every time we test a PR commit - and one of these actions breaking should not prevent the webpage from getting deployed (as Tenzing did in the past two days).

@richarddushime could you maybe help to split the action into one that processes data (and is called daily or on request) - and a build action that uses the artefact from the data processing action to rebuild the website (daily - after the data processing - and after each PR/commit)?

[richarddushime]

I will fix this ASAP
Thanks

[LukasWallrich]

Great progress on this!

Two small things:

• can we avoid code duplication? Currently, the code is repeated in the build action and the data processing action, which is likely to lead to bugs over time
• can we pull the forrt cv (in static/files) from this repo: https://github.com/forrtproject/cv

[LukasWallrich]

@richarddushime thanks for making it more robust - but Google Scholar now continuously fails, so we need to fix that. Also, can we make failures more visible - e.g., generating issues/issue comments?