Nest the script-update-processor page UNDER the update-request-processors page

[epugh]

The script-update-processor page should be nested:

However, I can't figure out why this isn't working in the ref guide!

[epugh]

See these errors message when generating ref guide:

> Task :solr:solr-ref-guide:buildLocalAntoraSite
{"level":"error","time":1725715956117,"name":"asciidoctor","file":{"path":"/Users/epugh/Documents/projects/solr-epugh/solr/solr-ref-guide/build/site-staging/modules/configuration-guide/pages/solr-plugins.adoc","line":64},"source":{"url":"https://github.com/epugh/solr.git","local":"/Users/epugh/Documents/projects/solr-epugh/.git","worktree":"/Users/epugh/Documents/projects/solr-epugh","refname":"fix_ref_guide_nesting","reftype":"branch","startPath":"solr/solr-ref-guide/build/site-staging"},"msg":"dropping cells from incomplete row detected end of table"}
{"level":"error","time":1725715964431,"name":"asciidoctor","file":{"path":"/Users/epugh/Documents/projects/solr-epugh/solr/solr-ref-guide/build/site-staging/modules/getting-started/pages/solr-admin-ui.adoc","line":172},"source":{"url":"https://github.com/epugh/solr.git","local":"/Users/epugh/Documents/projects/solr-epugh/.git","worktree":"/Users/epugh/Documents/projects/solr-epugh","refname":"fix_ref_guide_nesting","reftype":"branch","startPath":"solr/solr-ref-guide/build/site-staging"},"msg":"dropping cells from incomplete row detected end of table"}
{"level":"error","time":1725715972214,"name":"asciidoctor","file":{"path":"/Users/epugh/Documents/projects/solr-epugh/solr/solr-ref-guide/build/site-staging/modules/query-guide/pages/query-syntax-and-parsers.adoc","line":69},"source":{"url":"https://github.com/epugh/solr.git","local":"/Users/epugh/Documents/projects/solr-epugh/.git","worktree":"/Users/epugh/Documents/projects/solr-epugh","refname":"fix_ref_guide_nesting","reftype":"branch","startPath":"solr/solr-ref-guide/build/site-staging"},"msg":"dropping cells from incomplete row detected end of table"}

[github-actions]

This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be familiar with the code area and/or notify the [email protected] mailing list. To exempt this PR from being marked as stale, make it a draft PR or add the label "exempt-stale". If left unattended, this PR will be closed after another 60 days of inactivity. Thank you for your contribution!