using github-readme-stats-action and github-stats-extended

### Have you checked that your feature request isn't already filed?

- [x] I read through [FAQ](https://github.com/alshedivat/al-folio/blob/main/docs/FAQ.md) and searched through the [past issues](https://github.com/alshedivat/al-folio/issues), none of which addressed my feature request.
- [x] Yes, I have checked that this feature request isn't already filed.

----

Hi, I am a maintainer of [github-stats-extended](https://github.com/stats-organization/github-stats-extended) and [github-readme-stats-action](https://github.com/stats-organization/github-readme-stats-action/), which are actively maintained successor projects of github-readme-stats. We recently got a feature request in [github-readme-stats-action#67](https://github.com/stats-organization/github-readme-stats-action/issues/67) from a user who used al-folio for their website and wants to generate the repository cards via github-readme-stats-action. This is how I learned about your project - very cool work. :) I then noticed that your users have opened several issues here about the repo cards not working (e.g. https://github.com/alshedivat/al-folio/issues/3539, https://github.com/alshedivat/al-folio/issues/3388, https://github.com/alshedivat/al-folio/issues/2625).

So first I would like to propose **changing the repo card URLs** in your template from using the original, now unstable [github-readme-stats](https://github.com/anuraghazra/github-readme-stats) to github-stats-extended. github-stats-extended is stable, actively maintained and [backwards-compatible](https://github.com/stats-organization/github-stats-extended/blob/master/docs/fork.md#compatibility-notes) with github-readme-stats. If you agree, I would be open to making the necessary changes in al-folio.

Since the mentioned feature request we got was about using github-readme-stats-action for the al-folio generated website, I wonder what you think about an additional **integration between al-folio and github-readme-stats-action**. github-readme-stats-action doesn't generate SVGs on the fly on a server, instead it runs in a GitHub Action workflow and commits generated SVGs to the user's repository. If you're interested, this could either be included as an optional part of the the al-folio Action workflow or you could instruct your users how to set up github-readme-stats-action themselves. My main question here is if you would be interested in such an integration between the two projects. Because the mentioned feature request specifically asked for github-readme-stats-action to add an option for automatically iterating over all repositories owned by the user, and adding this only makes sense if users will actually be able to use github-readme-stats-action together with al-folio.

Please let me know your thoughts about switching to github-stats-extended and about an integration between al-folio and github-readme-stats-action. Cheers!