Use configuration so that empty page callbacks can be exported and imported

Currently, empty_page callbacks are saved in the database and are effectively treated as 'content'.

I propose maintaining the callbacks using the configuration system instead. This means that callbacks can easily be exported to code and managed through dev/stage/production environments, similar to other configuration throughout the site.