docs: add FinTech data quality framework use case guide

[mitalidaduria]

This PR adds a comprehensive 'FinTech Data Quality Framework' guide to the documentation under data quality features.

It outlines how to handle 3 critical financial data failure modes (settlement mismatches, orphaned records, and latency violations) using OpenMetadata's native profiling and test suites (such as columnValuesToBeBetween, columnValuesToBeUnique, and null prevention tests). This bridges platform capabilities with a highly requested industry use case.

[ayush-shah]

docs.json redirects this modified route to the unchanged canonical v1.13.x/api-reference/main-concepts/metadata-standard page, so none of this replacement is published; the PR also adds no FinTech guide matching its title. Add the guide under a current versioned path with frontmatter and register it in docs.json, and revert this redirected duplicate.

[ayush-shah]

Defect-first review on head cc1f8a0:

• [P1] Resolve the docs.json conflict. Conflict markers at lines 1495–1507 make the file invalid JSON, so Mintlify cannot load navigation. Retain the intended page entry and the existing Bulk Import group.
• [P2] Register a publishable guide path. The new navigation target does not exist; the guide is under content/main/... without page frontmatter. Move it to the registered versioned path with frontmatter or register an existing publishable path.
• [P2] Use a referential-integrity test for orphan records. columnValuesToNotBeNull only rejects nulls; an orphan key can be non-null while lacking a parent. Use a custom SQL or referential comparison and keep null validation separate.
• [P2] Replace the nonexistent freshness test. tableRowCountToBeGreaterThan is unavailable, and row count does not compare event time with ingest time. Use a supported freshness test or concrete SQL over MAX(created_at).
• [P2] Remove the unrelated glossary change. The canonical metadata-standard file adds an ML glossary unrelated to this FinTech guide and overlaps #331. Revert it from this PR.

Validation: jq fails on the current docs.json; the navigation target and test-definition searches were checked against the exact head.

[ayush-shah]

Follow-up on the latest review: all five items remain on head cc1f8a0—docs.json still contains conflict markers; the registered guide target is missing; the orphan check still uses not-null; the freshness test is unavailable; and the unrelated glossary remains. Please resolve these before re-review.

[ayush-shah]

Follow-up on the July 27 review: head cc1f8a0 is unchanged. docs.json still contains conflict markers at lines 1495–1507; the registered guide target is still missing while the guide remains under content/main/... without frontmatter; the orphan guidance still uses columnValuesToNotBeNull; the freshness guidance still names tableRowCountToBeGreaterThan; and the unrelated ML glossary remains. Resolve these five items before re-review.

[ayush-shah]

Thanks for the work here. After reviewing our documentation direction, we’ve decided not to maintain standalone FinTech or payments-domain examples in the docs. These PRs are also broader than the scope we want to support.
We’ll close this PR without merging. If the underlying concepts are still needed, they can be proposed later as a focused, industry-neutral documentation update.