Allow editors to index their records

[tylerjmchugh]

Currently there is no clear way for an editor to index their record.

There are several workaround ways that a user can trigger the indexing of a record. For example the addToUserSelection (/{portal}/api/userselections/{selectionIdentifier}/{userIdentifier}) endpoint can be used by guests and will trigger the indexing of the records added to the selection.

It seems that if even a guest can trigger the indexing of a record there should be some way for an editor to trigger the indexing explicitly for their records.

This PR aims to fix this issue by updating the index (/{portal}/api/records/index) endpoint to allow editor of the records instead of restricting to Administrators. The UI is also updated to show the Index record option in the manage record menu.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation