Disable plugin management via the admin interface

[jakecoble]

This also replaces the docker-compose.yml with a shell script out of necessity.

This does not inform the user about why the feature isn't working or what to do about it. That's waiting for a resolution on ether/etherpad-lite#6390

[narthur]

Great work!

[narthur]

Question--I see that docker-up.sh spins up both etherpad and postgres for local dev. How are you planning to spin up etherpad when it's running in its own server, separate from the postgres server?

[narthur]

Also what do you think of moving docker-up.sh and docker-down.sh to the scripts dir to keep all the shell scripts together? 🤔

[jakecoble]

I'll split the postgres server into something like docker-up.dev.sh

I can see the argument for moving the scripts into the scripts directory, but I also think it makes sense to have "project level" scripts in the project root and "data level" scripts in the scripts directory. Similar how you you might not include "eslint.config.js" or similar in a src/ directory since it's part of defining the project. I don't feel strongly either way.