Fund the remaining shared infrastructure work

It's easy to find people willing to fund or work on the flashier parts of CKAN, and there is some funding for core work such as meetings and preparing releases. But there are a few important things that aren't getting addressed.
1. Security issues

There are a small number of known issues that high profile sites work around by implementing workflows and tight controls over users and data published. Everyone else would benefit from a more-secure-by-default CKAN.
2. Technical debt

CKAN, has some parts that should be replaced or removed. This work doesn't add any new features and worse, threatens to break upgrades for existing sites and extensions. It is necessary work though. Unless performance and technical limitations are addressed they will grow and start turning users away from CKAN.

Some of those issues are labelled here: https://github.com/ckan/ideas-and-roadmap/labels/technical%20debt

No source files, tests, or entry points are named. Start by reviewing the technical-debt label linked in the issue and the known security work, then define a concrete, scoped item before implementation can begin. Done would require an agreed scope and funding rather than a single code change.

Written by the indexing model from the issue text.