GroundMapping: maximumRange=-1 isn't a valid action

[Star-Feel]

Describe the bug
When using GroundMapping with maximumRange=-1, its behavior is abnormal and it can't get access information normally. However, when maximumRange=1e9, it turns to be normal.

To reproduce
Using GroundMapping module

1. Set maximumRange=1e9, we can observe sat-target access information.
2. Set maximumRange=-1, accessOutMsgs.read().hasAccess are always 0.

Expected behavior
When maximumRange=-1, the output '1' in hasAccess should be not less than the one when maximumRange=1e9

Screenshots

Desktop (please complete the following information):

• OS: WSL
• Version: 2.3.26.0
• Python version: 3.11.10

Additional context
In basilisk/src/simulation/environment/groundMapping/groundMapping.cpp, I found that the function checkInstrumentFOV() (line 188), if ((boresightNormalProj >= 0) && (boresightNormalProj <= this->maximumRange)){, doesn't consider the -1 case, which is necessary for the access computation. It is possible that the problem here is causing the above bug.

[schaubh]

Thanks for the feedback. We'll look into that.