Add '<browse>' links matching those in AdminUI

[aydun]

Overview

This adds '' paths to the schema xml for use by #26887 for paths used in AdminUI.

Before

Not redirected to a browse page in some cases.

After

Redirected in more situations.

Technical Details

Comments

@colemanw Some of these work (ie following the sequence in #26887 goes to the browse page), but some don't. Eg: contact subtype, relationship type, financial accounts

[civibot]

Thank you for contributing to CiviCRM! ❤️ We will need to test and review the PR. 👷

Introduction for new contributors

• If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
• A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
• A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
• If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
• Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
• A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
• To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
• For more information about contributing, see CONTRIBUTING.md.

Quick links for reviewers

• ➡️ Demo site for this PR
• 📖 Review standards
• 🗒️ Review template (brief or verbose)

[colemanw]

@aydun patch failed, probably a merge conflict because your branch is slightly out-of-date. Try this:

git reset --hard HEAD~1 # delete your setup.sh commit
git pull --rebase origin master
./bin/setup.sh -g
git commit -a --amend # no need for a separate commit for setup
git push -f

[aydun]

Thanks @colemanw - that worked