MDL-19776 make sure contexts are fully initialised after each core upgrade, it is relatively cheap, so it should not cause any problems

MDL-23106 all tables created in upgrade.php MUST be present in install.xml - we will most probably drop the two old blocks tables before release but we can not allow exceptions like this, sorry

MDL-23106 removing unnecessary conversion of message_providers data - not installed yet in regular upgrades now

MDL-23106 fixing 2.0 upgrade paths - moving core table tweaks to the very beginning so that it is available for the whole upgrade

MDL-23104 cleanup after loancalc, lams, exercise and journal if no instances present - these were moved to contrib and we do not want them to appear on during upgrade page if not used at all

webservice MDL-22255 fix moodle_user_get_users_by_id() ws function when no custom field are returned

community hub MDL-23014 add private hub to the searchable hub list + use private token to search on a hub when a private token is available

Our rationale before was to stick to the ISO-3166 standard no matter what, since we don't want to get involved in territorial issues.  However, in this case no information is lost and it would make a lot of people happier (and no one unhappy, I think), so I'm going to make an exception.  Hope it's not a can of worms.