fix: Cache the Config

[ross-p-smith]

Purpose

Fixes #647

We use the higher-order functions to decorate the get_active_config_or_default method with a cache. We also invalidate the cache when we save the config.

However, because there are 2 applications, we display some text to tell the user that they will need to restart the Chat App to invalidate the cache

[github-actions[bot]]

Coverage Report •

File	Stmts	Miss	Cover	Missing
code/backend/batch/utilities/helpers/config
config_helper.py	138	0	100%
code/backend/pages
04_Configuration.py	135	135	0%	1–9, 11–12, 14, 21, 28, 30, 35–44, 47–48, 51–62, 64–65, 67–69, 73–74, 86–90, 93–94, 98–100, 103–104, 107–108, 111–112, 135, 137–138, 140–144, 146–149, 152–156, 163–164, 174–176, 178, 198–199, 201, 203, 209, 217, 225, 232–233, 240, 242–243, 247, 255, 261, 268, 286–290, 296–297, 316–317, 321, 323–324, 347, 381–382, 386–387, 390–391, 394–397, 399–400, 402–404, 406–409, 411–412
TOTAL	2431	672	72%

Tests	Skipped	Failures	Errors	Time
206	0 :zzz:	0 :x:	0 :fire:	12.338s :stopwatch:

[ross-p-smith]

how much effort do you think it would be to add an endpoint to the chat app

I was actually thinking about this. However, I think the problem would be the dependency graph of the deployment. We would need the chat app deployed to be able to get the url (unless we did it by convention), but the backend is what is deployed last; and it would be the admin app calling the backend. But not saying no, let me give it a weekend thought!

[adamdougal]

how much effort do you think it would be to add an endpoint to the chat app

I was actually thinking about this. However, I think the problem would be the dependency graph of the deployment. We would need the chat app deployed to be able to get the url (unless we did it by convention), but the backend is what is deployed last; and it would be the admin app calling the backend. But not saying no, let me give it a weekend thought!

Ah good point! I guess another option could be to have a ttl on the cache, is that possible with func tools?