Update to Mukurtu 4

[nichgray]

Just making an issue for this giant task so it's on the dev radar. The production version of Mukurtu 4 (based on Drupal 8) is scheduled to be released in mid-2022. Support for earlier versions of Mukurtu (and Drupal 7) will end in 2022, so this is a high-priority update. A beta version is scheduled to be released to the public in early to mid-2022.

Note that Mukurtu has said this will be a major change that will (among other things) update how batch imports are handled. It is also likely to affect the display in various ways, so several of the other issues in this repo should probably wait until after this update. From support: "Mukurtu 4 is a substantial technical departure from Mukurtu 2 and 3. You will not be able to “upgrade in place”, the same way you update from 2.1.5 to 2.1.6, etc.… Our team will provide migration pathways to bring your content forward to a new Mukurtu 4 site."

For more information: https://mukurtu.org/mukurtu-4/

[nichgray]

The current, interim solution while we are waiting on the release of Mukurtu 4 is to update the production site to 3.0.2 and leave the dev site at 2.1.5 (the last version for which batch imports were possible). This way the public-facing site has the latest security updates. Here is a list of issues with the more recent versions of Mukurtu (2.1.6 and later) with this site's customizations that are preventing us from using those for anything but prod:

• batch imports do not work because of an issue noted by Mukurtu
• something is up with the community/protocol configuration such that the community "Community Advisors" (the public access community) cannot be selected for new items, and neither community nor protocols can be adjusted for existing items

The current plan should not require items to be added to the production version of the site, so we are not planning to address these issues at this time. New content will be added to the dev version of the site, which will be used to overwrite the production version, and then the production version will be updated and recustomized again to make that content available. This process is time-consuming and should occur infrequently, so items should be staged for addition if possible.