Closes #19014
Summary of the issue:

Since #18323, there has been LaTeX included in the User Guide. However, it was not parsed, just left as source.
Description of user facing changes:

The newly added LaTeX is now parsed to MathML, meaning it may be interacted with using MathCAT, and should be displayed in modern browsers.
Description of developer facing changes:

None
Description of development approach:

    Added l2m4m to as a dependency.
    Added its LaTeX2MathMLExtension to the extensions used when converting the user guide.
    Whitelisted the MathML tags that we currently use in the user guide.
    Allowed the display attribute on <math> tags.
    Added an attribute filter callable that strips the display attribute on <math> tags if its value is inline, as this is redundant.

Fixup #18323

### Summary of the issue:

`mathCATDir` is a property of `NVDAState.WritePaths`, even though it is
not writable by non-elevated installed copies, and it doesn't seem like
we even want to write to it.

### Description of user facing changes:

None

### Description of developer facing changes:

`mathCATDir` is now a property of `NVDAState.ReadDirs`.

### Description of development approach:

Moved `mathCATDir` to `NVDAState._ReadDirs`.
Searched for usages of `mathCATDir` in `source/` and updated them.

### Testing strategy:

Ran from source and interacted with MathML in Firefox.

### Known issues with pull request:

None

Follow-up of #18323.
Summary of the issue:

Some MathCAT options were unclear and hard to understand.
Description of how this pull request fixes the issue:

Cleanup UI and documentation.
Testing strategy:

Tested that settings changes appear as expected. Alpha testing.

Summary of the issue:

When MathCAT has been integrated in NVDA (#18323), many translatable language names have been added. These language names are not used by MathCAT, nor by NVDA itself. Thus this addition only represents extra work for translators and unused code in the code base.
Description of user facing changes:

N/A
Description of developer facing changes:

No more unused languages to translate.
Description of development approach:

    Removed the languages added in Integrate MathCAT into NVDA #18323.
    Kept the most modern annotation style done in the same file.

Follow-up to #18323, #19373 and #19613

### Summary of the issue:

Since the introduction of MathCAT into NVDA in #18323, NVDA has
persisted MathCAT settings to a YAML file . This is at odds with current
project configuration standards, which use either configobj ini files,
or JSON. This also duplicates settings, as they're also saved to
`nvda.ini`.
Originally, these were stored in `%AppData%\MathCAT\prefs.yaml`, but as
of #19373, they are saved to `mathcat.yaml` in NVDA's config directory.
In neither case was `shouldWriteToDisk` checked before saving the
preferences. Additionaly, [NV Access's Corporate & Government
page](https://www.nvaccess.org/corporate-government/) states "To prevent
NVDA users from modifying their configuration or add-ons directly, user
write access to [`%APPDATA%\nvda`] must also be restricted". If
implemented, this would have stopped users from changing their MathCAT
settings in memory, as they had to be saved to YAML to be loaded by
MathCAT.
In #19613, the logic was changed to programmatically apply these
settings with `libmathcat.SetPreference`, which should solve the problem
of users without write access to their NVDA config directory being able
to change their MathCAT preferences. However, the code that wrote the
settings to the YAML file was not removed, nor did it contain any error
handling.

### Description of user facing changes:

None, but may avoid some errors in the logs.

### Description of developer facing changes:

Pyyaml is no-longer a dependency.
`mathPres.MathCAT.preferences.MathCATUserPreferences.save` has been
renamed to `apply`, and no longer saves the settings to YAML. Settings
persistance is handled by NVDA's configuration system.

### Description of development approach:

Removed the code that wrote MathCAT preferences to YAML, and any code
that only it depended on. Renamed `save` to `apply` using VS Code's
refactoring tool. Searched the repo for `yaml` and after confirming that
we don't rely on `pyyaml` anywhere else, ran `uv remove pyyaml`.

### Testing strategy:

Tested by loading the [Wikipedia page on the quadratic
formula](https://en.wikipedia.org/wiki/Quadratic_formula) in firefox.
Located some math and read it. Changed settings one at a time and tested
that they were applied correctly. Restarted NVDA and ensured that the
new settings were still present.

### Known issues with pull request:

None known