11716 - Fix usage of resolve(reverse()) to check if FORCE_SCRIPT_NAME…

[bferguso]

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description of Change

The resolve(reverse(<view name)) pattern doesn't work if the FORCE_SCRIPT_NAME is setting is used when hosting behind a reverse proxy in a sub-path. This checks to see if the FORCE_SCRIPT_NAME is used to and removes the prefix to correct the issue.

Issues Solved

Closes #11716

Checklist

• I targeted one of these branches:
  • dev/8.0.x (under development): features, bugfixes not covered below
  • dev/7.6.x (main support): regressions, crashing bugs, security issues, major bugs in new features
  • dev/6.2.x (extended support): major security issues, data loss issues
• I added a changelog in arches/releases
• I submitted a PR to arches-docs (if appropriate)
• Unit tests pass locally with my changes
• I added tests that prove my fix is effective or that my feature works
• My test fails on the target branch

Accessibility Checklist

Developer Guide

Topic	Changed	Retested
Color contrast
Form fields
Headings
Links
Keyboard
Responsive Design
HTML validation
Screen reader

Ticket Background

• Sponsored by: Self Funded
• Found by: @bferguso
• Tested by: @bferguso
• Designed by: @bferguso

Further comments

[jacobtylerwalls]

Ah ah I get it now -- you're saying all we need to do is undo the call to get_script_prefix() inside reverse(), and we're in the same thread. Sorry for being slow on the uptake.

PR looks good!

[jacobtylerwalls]

Added coverage, test fails on main. The missing coverage is a code path mostly (only?) called from async paths, where we have basically zero test coverage. Would be a worthy challenge in some cases, but looking closer, this is code I think we want to improve on anyway (we have a module level function outside the request/response cycle creating a dummy request). Better to remove this code than test it.