Environmental impact of ChRIS and ChRIS plugins

This issue is not really related to _miniChRIS_, but is put here for consolidation with other issues with the "observability" label.

It would be cool if we could somehow measure the environmental impact of ChRIS and ChRIS plugins. I got this idea while talking to members of [OHBM SEA-SIG](https://ohbm-environment.org/) at [OHBM BrainHack 2022](https://ohbm.github.io/hackathon/).

Big data and cloud computing has a negative environmental impact. The easiest aspect of this to quantify would be the estimated "carbon emissions" caused by the energy used by computers.

https://codecarbon.io/ is a method to measure to estimate carbon emissions caused by Python programs. It might be useful.

Where in the architecture can we implement this? Ideally, we would do it at the level of the container runtime (runc, crun, apptainer) and then have this data be sent to CUBE. ChRIS_ui could display the information and guilt-trip the user, like how Google Flights does:


A much easier but unscalable proof-of-concept would be to create a ChRIS plugin that uses codecarbon.