Permit sort_name as a url parameter on advanced search

[eileenmcnaughton]

Overview

This lays the ground work for our metadata based approach to search forms in the contact form. Specifically it converts one field (sort_name) to be added by metadata and also to be supported via url (sort_name=x)

Before

Metadata based approach not extended to contact form

After

Approach extended - the one converted field is url-parseable

Technical Details

@monishdeb putting this up to show where I think we should be going on this

Comments

[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).

[eileenmcnaughton]

moved to parent

[monishdeb]

A baby step towards a larger goal. Nice :) Reviewing it now

[monishdeb]

Yup thanks for fixing the test failure :)

[eileenmcnaughton]

@monishdeb we also need to do basic conversions on a couple more forms - pledge is here #14431 & I think Case & Membership remain

(I've been doing small PRs for the basic converstions just to get the right functions in play)

[monishdeb]

@eileenmcnaughton I think such improvements will eventually help us to get the search by url params doable for all search forms right ?

[eileenmcnaughton]

@monishdeb yes!

[eileenmcnaughton]

@monishdeb you can see the PR that build on this - #14477 exposes sort_name but also some other fields that are already metadata-defined as url fields

[monishdeb]

Am happy with this patch. Tested on my local and worked fine. Merging it now

[eileenmcnaughton]

@monishdeb nice - I'll rebase that participant one then