[REF] Add contribution_id field to search using metadata instead of h…

[seamuslee001]

…ard codeded quickform html

Overview

Follow on from #16484 and this adds the contribution_id field using metadata rather than a hard coded quickform field. Doing it this way also allows for search urls such as /civicrm/contribute/search?reset=1&force=1&contribution_id=1 to be used

Before

Field added using hard coded quickform values

After

Field added using metadata

ping @mattwire @eileenmcnaughton @yashodha

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[jaapjansma]

• General standards
  • Explain (r-explain)
    • PASS : The goal/problem/solution have been adequately explained in the PR.
  • User impact (r-user)
    • PASS: The change would be intuitive or unnoticeable for a majority of users. who work with this feature.
  • Documentation (r-doc)
    • PASS: The changes do not require documentation.
  • Run it (r-run)
    • PASS: We have tested the advanced search and find contribution by searching on an existing contribution id. Both in dmaster and in the test site of this PR.
    • ISSUE:
• Developer standards
  • Technical impact (r-tech)
    • PASS: The change preserves compatibility with existing callers/code/downstream.
  • Code quality (r-code)
    • PASS: The functionality, purpose, and style of the code seems clear+sensible.
  • Maintainability (r-maint)
    • PASS: The change is trivial enough that it does not require tests.
  • Test results (r-test)
    • PASS: The test results are all-clear.

@eileenmcnaughton or @mattwire could one of you merge this PR?