v0.3.0 wordpress.org readiness

Getting ready for wordpress.org. An update moves everything by itself on the first load after it is installed.

What changes on an installed site

• The data directory moves from wp-content/bot-storm-radar-<random>/ to wp-content/uploads/bot-storm-radar-<random>/. The old directory is switched off at once and removed by itself about a day later. An early-protection line is pointed at the new place.
• The prefix is now botstormradar. Settings, bans, minute history, baselines and cron hooks move to the new names; nothing is lost.
• Hooks for developers are renamed to botstormradar_request_class, botstormradar_known_classes, botstormradar_actions, botstormradar_bans_changed, botstormradar_protected_changed and botstormradar_beacon_url_base; the constants to BOTSTORMRADAR_COUNTER_BACKEND and BOTSTORMRADAR_DEBUG_TIMING.

Change by hand, if you have them

• The nginx rule for the data directory: location ^~ /wp-content/uploads/bot-storm-radar- { deny all; }
• A hand-written include_once of the gate loader in wp-config.php: the path now has uploads/ in it. The Settings tab says so when it sees the old loader still being loaded.

Also

• readme.txt in the wordpress.org format, a build script with a wordpress.org flavor, translator comments on every string with placeholders, Plugin Check without findings.

Full list in CHANGELOG.md.