Hotfix 2023 08 08 (#606)

[egbot]

• Occurrence Voucher bugs

• Resolve error associated adding an occurrence as a checklist voucher from the occurrence details page
• Ensure that editing permissions are verified, to ensure that edit additions can't be applied by none authorized used.

• Identification Key

• Avoid warning when there are no terms set within the Glossary

• Occurrence Upload

• Expand back-mapping snapshot dbpk value capabilities to make use of occurrenceID identifiers, as well as catalogNumber

• Styling

• Minor working adjustment to header translation file template
• Resolve styling issues with button-icons and quick search default setup

• Documentation and Language translations

• Add documentation for installation a robots.txt file
• Fix issues with language translation terms interfering with submit button functions

• Security fixes reported by Qualys:

• Resolve issue with sanitation of occurrence search variables held within session storage
• Various variable sanitation updates
• Remove deprecated sanitation methods such as filter_var/FILTER_SANITIZE_STRING
• Improve integer sanitation methods
• Add index redirects to avoid directory content viewing when this is not configured within web server

Pull Request Checklist:

• Features and backlog bugs should be merged into the Development branch, NOT master
• Hotfixes should be merged into both the Development and master branches (at the same time).
• All new text is preferrably internationalized (i.e., no end-user-visible text is hard-coded on the PHP pages)
• There are no linter errors
• New features have responsive design (i.e., look aesthetically pleasing both full screen and with small or mobile screens)
• Symbiota coding standards have been followed
• If any files have been reformatted (e.g., by an autoformatter), the reformat is its own, separate commit in the PR
• Comment which GitHub issue(s), if any does this PR address
• It is the code author's responsibility to merge their own pull request after it has been approved
• If this PR represents a merge into the Development branch, remember to use the squash & merge option
• If this PR represents a merge from the Development branch into the master branch, remember to use the merge option
• If the dev team has agreed that this PR represents the last PR going into the Development branch before a tagged release (i.e., before an imminent merge into the master branch), make sure to notify the team and lock the Development branch to prevent accidental merges while QA takes place

Thanks for contributing and keeping it clean!