fix(docs): tag aztec-nr-api records so they pass the search filter

[critesjosh]

Summary

Third in the series fixing search after #22861. Previous PRs (#23042, #23049) successfully indexed 14,773 records from 2,222 aztec-nr-api pages, but users still don't see those records in the dropdown search.

Root cause

The docusaurus-theme-search-typesense package ANDs a contextual filter into every search query:

// docusaurus-theme-search-typesense/src/client/useTypesenseContextualFacetFilters.ts
const languageFilter = `language:=${locale}`;
const tagsFilter = `docusaurus_tag:=[${tags.join(',')}]`;
return [languageFilter, tagsFilter].filter(Boolean).join(' && ');

The api-nr records have neither language nor docusaurus_tag set, because the typesense-docsearch-scraper only stamps those onto records scraped from docusaurus pages (it reads <meta name="docsearch:docusaurus_tag" content="..."> tags). Rustdoc-style nargo-doc pages don't emit those metas, so every api-nr record is missing the fields the theme filters on, so every api-nr record is filtered out of every dropdown query.

Fix

Three coordinated changes:

1. extra_attributes on the api-nr start_url (docs/typesense.config.json)

Stamp every api-nr record with the attributes the theme expects:

"extra_attributes": {
  "language": "en",
  "docusaurus_tag": [
    "docs-participate-current",
    "docs-root-current",
    "default"
  ]
}

These cover the three unversioned plugin contexts. The two versioned ones (docs-developer-${version} and docs-network-${version}) are appended dynamically by the workflow (see #3) so the static config doesn't go stale on version bumps.

Typesense's docusaurus_tag:=[<context-tag>] matches if the record's array contains the context tag, so the api-nr records will satisfy the filter from any plugin context.

2. field_definitions schema override (docs/typesense.config.json)

The scraper's default schema (scraper/src/typesense_helper.py v0.11.0) declares the wildcard .*_tag as string, so sending an array for docusaurus_tag would be rejected at import time. field_definitions overrides this — but it REPLACES the entire default schema rather than merging, so the full default field list is reproduced verbatim with one targeted change: docusaurus_tag is added with type string* (accepts both string and array) before the .*_tag wildcard. Existing docusaurus records continue to work because they pass docusaurus_tag as a single string from a meta tag, and string* accepts that too.

3. Derive versioned tags at scrape time (.github/workflows/docs-typesense.yml)

Read developer_version_config.json and network_version_config.json, build the docs-developer-${mainnet}, docs-developer-${testnet}, docs-network-${mainnet}, docs-network-${testnet} strings (dropping empty/duplicates), and use jq to append them to the api-nr start_url's docusaurus_tag array before passing the config to the scraper. This way the static JSON never holds version-specific values that need manual updating.

The workflow run also switches to set -euo pipefail so a jq derivation failure aborts the run rather than feeding an empty config to docker.

Caveats

• Existing 14,773 api-nr records in the production collection are stale until the next scraper run rewrites them. The scraper alias-swaps to a fresh collection on each run, so no manual purge is needed.

Test plan

• Manually dispatch Docs Scraper workflow on this branch via workflow_dispatch.
• Confirm scraper run reports Nb hits ≈ 27,000 (no regression in record count).
• Confirm no schema-validation errors in the run log.
• Confirm the workflow log echoes the derived docusaurus_tag values matching the current docs versions (e.g. docs-developer-v4.2.0, docs-network-v4.2.0).
• After merge, search docs.aztec.network from the homepage, /developers/, and /operate/ for an Aztec.nr identifier (e.g. ContractClassId, balance_set, compute_log_tag) and confirm API reference pages appear in the dropdown in all three contexts.