Refresh the vendored MEOS-API artefacts

[github-actions]

make vendor-meos-api regenerates vendor/meos-api/ from MEOS-API
master and the MobilityDB headers it parses, and the result differs
from the committed copy.

Opened by the scheduled Vendor drift (MEOS-API) run, which reruns
daily and updates this pull request while the difference stands.

[estebanzimanyi]

Master carries these artefacts generated with the object-model oracle in place: the parity report reads status: audited with oraclePath: pymeos/factory.py, every divergence explained by a curated correction and none outstanding, and the catalog is the larger, later one.

The refresh on this branch carries the oracle-unavailable degradation, whose oraclePath names one runner's temporary directory. Applying it drops the audit and installs a path that no regeneration reproduces, and an artefact carrying such a path differs from every regeneration of it, which is the condition that holds the drift gate red.