docs: add business-friendly ML glossary with payments domain examples

[mitalidaduria]

This PR adds clear, business-friendly translations and payments-domain examples for key technical data terms (Model Drift, Data Lineage, Feature Engineering, Label Skew, and Data Quality SLAs) to bridge the operational gap for business stakeholders referencing OpenMetadata's core conceptual glossary.

[kiran1287]

As per technical writing standards, could you please fix these before merge:

1. Add an introductory sentence — The ### Machine Learning & Data Governance Expansion heading is immediately followed by the #### Model Drift subheading with no body text in between, which the style guide flags (no heading should directly follow another heading). Suggested addition right after the section heading:

   "The following terms bridge common machine learning and data governance concepts to business-friendly language, with payments-domain examples showing how each one shows up in practice."

2. Move the colon outside the bold markers — Field labels currently bold the colon along with the label text, e.g. **Technical Definition:**. Move it outside the asterisks instead: **Technical Definition**:. Apply this to all three labels (Technical Definition, Business Translation, Payments Example) across all five terms.

3. Remove the numbering from the term headings — #### 1. Model Drift, #### 2. Data Lineage, etc. imply a sequence or ranking, but these are five independent, equally-weighted glossary terms rather than sequential steps. Drop the numbers so headings read as #### Model Drift, #### Data Lineage, #### Feature Engineering, #### Label Skew, #### Data Quality SLA (Service Level Agreement).

Thanks!

[mitalidaduria]

Hi @kiran1287, I've updated the file with the introductory sentence, changed the subheadings to the proper heading level without numbers, and moved the colons outside the bold formatting. Ready for another look!

Withdrawing approval — needs another look before merging.

[ayush-shah]

Confirmed P1 finding on current head e219e8844cf78b39178697ddd201ea865a9dfc83:

v1.13.x/main-concepts/metadata-standard.mdx:1 now starts directly with ## Machine Learning & Data Governance Expansion. This removes the page's required frontmatter, H1, and the existing metadata-standard/schema overview, replacing the page rather than adding a glossary section. The repository guidance requires frontmatter on every page, and this route is still the canonical metadata-standard page. Please restore the original page structure and content, then append the glossary in an appropriate section or move it to a dedicated page wired into docs.json.