Considering archiving/rewrite in favor of official CKAN Docker compose setup

[rzmk]

A while back one of the reasons I set up the ckan-devstaller project was to speed up installing CKAN for extension development since I used to use a virtual machine approach where each project had a separate virtual machine that needed CKAN installed. Nowadays I simply use a modified version of the ckan/ckan-docker repo to help develop ckanext-gztr and I would think with enough polish that the ckan/ckan-docker repo would be more ideal for CKAN extension development. Setting up environments based on that polished setup could work. There is also ckan-pilot by Keitaro that is an alternative to ckan-devstaller (though I had issues when using it). I also think it'd be good to document how to set up a development environment in the extensions modernization docs using the ckan/ckan-docker setup and perhaps automate things based on that setup.

So either archiving/deprecating ckan-devstaller or doing a codebase rewrite to focus on using ckan/ckan-docker (and/or a modified version(s) of it) could be reasonable, if I ever get the time.