* 3.3 release notes scaffolding
* Add modified version of internal release notes (to be further improved)
* slightly updated release notes
* Add another char to CSE ID regex
* Add 3.3 to version switcher
* removed empty sections
* Amend text about DC2DC in release notes.
* Move DC2DC description to Release Notes
* Add links to highlights and release notes
* Add placeholder for 3.3 upgrading
* renamed from server-global to server-level
* changed wording
* port changes from branch 3.3.0
* Update VERSIONS with 3.3 CSE IDs and sitemap settings
* Correct custom search IDs, sitemap and edit URLs
* deploy versions through shell script from central places
* shellcheckify
* shellcheck, indent
* move all configs into one file
* add settings
* one more char that may occur in ids
* add per book version, its not yet the right ids.
* Update VERSIONS
Lower prio and keep 3.2 CSEs until 3.3 release (latest docs should have highest prio, followed by devel and the old docs, 3.1 and 3.0; 2.8 might be more important than 3.0 and 3.1, because some users may still use it in production and can't upgrade).