Investigate Self-Hosting of Avataaars

[SelinaBuff]

Description:

Currently, avatars on the landing page are fetched from getavataaars.com, an external service. To improve control over dependencies and optimize performance, we want to explore the possibility of self-hosting this library.

Requirements:

• The Avataaars library should be self-hosted to eliminate external dependencies, if technically feasible.
• If self-hosting is not possible, document the integration, including what data is exchanged and how the service operates.
• Evaluate the feasibility of self-hosting the Plausible init script, currently loaded from https://inolytics.inovex-gpt.fra.ics.inovex.io/js/script.js, to ensure full control over analytics.

[Planlos5000]

It would be possible to self host the getavataaars.com if we build the image. There is no official Dockerimage.
But the landing page uses the random-avatar-generator which sends a request to avataaars.io to generate the avatar and it is not possible to easily change the url for the package.

Scrumlr uses the avataaars Package which does not send any requests. We should investigate if we could also use this package for the landing page.

[Schwehn42]

Scrumlr uses the avataaars Package which does not send any requests. We should investigate if we could also use this package for the landing page.

Should definitely be possible, the landing page uses random-avatar-generator while scrumlr itself uses avataaars. The former makes the HTTP call while the latter is used locally. The downside is the the latter has no native randomization logic, but luckily we've already implemented that (see https://github.com/inovex/scrumlr.io/blob/bf17d359380b0aa774b9954b6cece468f4fb4fee/src/components/Avatar/Avatar.tsx) so we can likely just reuse that.