Backport of 'Add scoped Orbit grep endpoint' to 19.4

What does this MR do and why?

Backport of !256404 (merged) to 19.4.

This adds the scoped Orbit grep endpoint. It is a feature, not a bug fix, and is backported at the team's request. A release manager exception covers this feature backport. The original is merged on the default branch and deployed to GitLab.com.

!264072 (merged), which brought in the Orbit code this depends on, has merged into 19-4-stable-ee. The branch is now a single commit cherry-picked directly on 19-4-stable-ee.

The cherry-pick applied cleanly, and the diff is identical to the original 8826bca0 (same patch-id; 12 files, 1637 additions, 0 deletions).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. (This backports a feature at the team's request.)
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• Required labels have been applied to this merge request
  • severity label and bug subtype labels (if applicable)
  • If this MR fixes a bug that affects customers, the customer label has been applied.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the E2E Omnibus GitLab EE pipeline (triggered by thee2e:test-on-omnibus-ee job) has succeeded. If it has failed (or shows warnings), investigate the failures. If you determine the failures are unrelated, you may proceed. If you need assistance investigating, request help in the #s_developer_experience Slack channel to confirm the failures are unrelated to the merge request.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).
• Once the backport has been merged, the commit changes will be automatically deployed to a release environment that can be used for manual validation. See [after merging runbook] for details.

Agent context

• Cherry-picked with git cherry-pick -x 8826bca0a708 directly onto 19-4-stable-ee, no conflicts. git range-diff against the original shows only the added (cherry picked from ...) trailer.
• Rubocop is clean on the 9 changed Ruby files. Specs were not run locally; CI is the spec gate.