fix(schema): register steps 361-367 so an upgrade can leave the schema page

[mastacontrola]

Regression from #1338, reported from a live deploy. An upgraded server cannot leave ?node=schema.

What I got wrong

commons/schema.php is not one large array — it is ~326 separate $this->schema[] = [...] statements. I appended #1338's seven UPDATEs before the file's final ];, so they joined the previous step's array and the step count never moved, while FOG_SCHEMA went 360 → 367.

count($this->schema) == mySchema == 360
  -> $hasIndexed false, updater applies nothing
  -> version written from the loop variable, so never advanced past 360
  -> mySchema < FOG_SCHEMA stays true forever
  -> DatabaseManager::establish() redirects EVERY request to ?node=schema

The schema page then reports nothing to do and answers the POST 204, which jQuery reports as statusText nocontent and $.notifyFromAPI renders as a red "Generic Error" toast, looping.

A fresh install was fine — the statements still ran inside that last step. That is exactly why every schema job in CI stayed green: they build from scratch and never replay an upgrade from an existing version.

The fix

Seven real $this->schema[] = [...] entries, labelled 361-367, so array_slice($this->schema, 360) yields them and the last sets the version to 367. FOG_SCHEMA is unchanged — 367 was always the right number (325 literal appends + the 35 the keySequences loop writes = 360 before this).

The part that matters more

tests/schema-gate.test.php already existed for this exact bug class and did not catch it. It compared $schema < $highest, enforcing only the case where FOG_SCHEMA is too low. #1338 made it too high, and with no new label and no new append there was nothing for its other two checks to see either.

Its own docblock already said the high side is "worse than stranding a step" — a server cannot leave the schema page to fix itself. The comparison is now equality, and the message says which direction failed and names the usual cause.

Mutation-verified both ways:

• reproducing fix(ui): seven task icons render blank after the Font Awesome 7 migration #1338's exact shape (statements inside the previous step, FOG_SCHEMA 367, no new label/append) → fails, naming the cause
• FOG_SCHEMA too low → still fails as before

Full suite: 144 passed, 0 failed.