MDL-44669: mod/assign: fix batchoperations JS when using select all checkboxes.
MDL-29572 Grade Import: Avoid creating invalid temporary rows; Provide feedback on error
MDL-33486 wiki: allow searching individual wikis
MDL-41895 conditions Show details of grouping restriction
MDL-42195 Bootstrap: Make bootstrap responsive images "opt-in".

This responsive image behaviour prevents setting of image sizes in text editors,
as well as a string of pix icon bugs / profile image bugs across Moodle.

We are switching to Bootstrap 3 syntax where you need img-responsive class to images
that want this behaviour.
MDL-43021 course: corrections to the shortname and idnumber uniqueness validation
Automatically generated installer lang files
MDL-44938 SCORM: missing constant definition during upgrade.
MDL-44738 SCORM: don't show heading when in popup mode.
MDL-44873 theme_bootstrapbase: Added support for notifytiny class
MDL-44873 behat: Added suppport for clean error class.
MDL-40872 Restore functionality of showrecentsubmissions setting
MDL-40843 recent_activity: corrections to grouping and user fields
MDL-40843 workshop: show user names in recent activity
MDL-40843 workshop: sort entries in recent activity block by time
MDL-44891 Behat: Add step to check attribute

This commit creates a Behat step of the form:

Then the "title" attribute of "Toggle visibility" "button"
should contain "Show"

This is useful because unless I missed something there is currently
no step that checks attribute values; this seems like a simple
generic step. Behat is intended to check user-visible effects in
the resulting HTML, and sometimes these effects are implemented
using attribute values (two common examples are the alt= attribute,
which is visible to screenreader users, and the title= attribute,
which is visible to all users; there's also the src attribute of
images, and lots of other possibilities too).
MDL-38183 themes: Removed redundant css rules for #adminsettings .form-overridden from standard and formal_white.
MDL-41511 blocks: improved how custom block regions were being rendered.

There is a new theme property 'blockrendermethod' that can be set by the
theme in its config.php and tells Moodle what method it is using to render
blocks in the layout files.
Either blocks, or blocks_for_region.
Then when adding custom block regions to a page content we ensure we use
the same method the theme is using elsewhere.

This is really a hack becuase we (I) didn't properly deprecate
blocks_for_region when I added the blocks method.

Conflicts:
	lib/outputlib.php
MDL-41551 blocks: added tracking and recognition of custom block regions
MDL-41551 theme_base: improved custom block region handling for base