MDL-33789 theme_formal_white: fixed the heigh of the navigation bar even with "theme_formal_white | fontsizereference" set to 16 pixel
MDL-35187 /group: Changed page layout from 'standard' to 'admin' in group/index.php
MDL-35472: Prevent html tags appearing in page titles

Only a problem when formatstringstriptags is disabled
MDL-35437: mod_assign: Stop Moodle from giving out a notice when grading worksheets with missing columns are uploaded via 'Upload grading worksheet' option in the drop-down menu
MDL-35636 login/token.php: confusing 'create user token' log appearing before 'token user request'
MDL-34971 PHPunit test: user/externallib.php
MDL-35644 user_get_details: admin should be able to see description
MDL-33933 mod_forum: fix incorrect capability check
MDL-35662: Grant extension does not work when applied to multiple users in assignment grading interface
MDL-35637 group: Fix form submission error that occurs when GD version is not set.
MDL-34257 quiz 'secure' mode: PAGE initialisation order issues.
MDL-34657 test: verify CASE statements in ORDER BY clauses.
MDL-34657 datalib: function to generate user sort sql.

The purpose of this method is to ensure that when we display lists of
users in different places, the default sort order is consistent.

Having this code centralised in one place them makes it possible to
improve things accross the board, and there is an example of that here.
There is logic so that if we are searching for particular string, then
users with an exact match are sorted first.
MDL-34657 user sorting: consistent sorting everywhere.

This commit coverts everything in the codebase to use the new
users_order_by_sql function when sorting lists of users. More details in
the bug.

Note that this does not change places where users are displayed in a
sortable table, and the sort order comes from the table.
MDL-35370 cloze qtype: distinguish wrong & unanswered subqs

This affects the subquestions that appear as an embedded text input box.

There are three cases:
1. Input for subq left blank
2. Input for subq was wrong, and matched by a * wildcard.
3. Input for subq was wrong, and did not match any answer.

2. and 3. should look identical, apart from any feedback in case 2.

1. is different. The state should be displayed as "Not answered" even
though the mark for this part is still shown as 0.

There are some new unit tests for these cases.

Also, we slighly improve handling of , for decimal point in multianswer,
although there are still issues.

While working on this, I made some minor clean-ups in shortanswer and
numerical qtypes.
MDL-35620 question engine: should distinguish NULL and 0.

This only matters in an obscure edge case, but it is an edge case we hit
with one of the OU question types.

This load data code is processing the results of a LEFT JOIN, so is_null
is the correct logic.
MDL-35616 import YUI 3.7.2
MDL-30885 quiz: use formchangechecker during quiz attempts.

To avoid the possiblity of dataloss if a student tries to navigate away
having changed some answers.
MDL-34657 admin user selector: options were lost for ajax searches.

The subclass constructor must pass through the pass through any name or
options.
MDL-34657 user selector: bug with "keep non-matching selected users"