Fix yet another settings caching issue
Fix yet another settings caching issue

That api endpoint really is a tough nut. ETag calculation now also
takes full settings dump from settings plugins into account, because
those might be providing custom keys through custom on_settings_load
implementations, for which we will not notice any changes if we are
only looking at the effective config.

Of course, the more we put into that ETag calculation, the slower it will
be and the less sense it will make. Somewhat annoying :/

JackGavin13/octoprint-test-not-finished,Salandora/OctoPrint,MoonshineSG/OctoPrint,foosel/OctoPrint,Salandora/OctoPrint,beeverycreative/BEEweb,MoonshineSG/OctoPrint,Jaesin/OctoPrint,MoonshineSG/OctoPrint,Jaesin/OctoPrint,JackGavin13/octoprint-test-not-finished,beeverycreative/BEEweb,beeverycreative/BEEweb,beeverycreative/BEEweb,bicephale/OctoPrint,foosel/OctoPrint,bicephale/OctoPrint,foosel/OctoPrint,JackGavin13/octoprint-test-not-finished,bicephale/OctoPrint,MoonshineSG/OctoPrint,Jaesin/OctoPrint,Jaesin/OctoPrint,foosel/OctoPrint,Salandora/OctoPrint,Salandora/OctoPrint,JackGavin13/octoprint-test-not-finished,bicephale/OctoPrint