Feature Request:Make the isPathValid Service Configurable with Parameters

[BCKSELFDRIVEWORLD]

Feature request

Feature description

Currently, the isPathValid service considers a path valid as long as the costs are not lethal. However, in many scenarios, users might need more flexibility in determining what constitutes a valid path. For instance, there might be cases where paths with costs above a certain threshold (but below lethal cost) should also be considered invalid.

To address this, I propose introducing a parameter that allows users to specify the threshold cost for path validity. This would make the service more adaptable to different use cases and improve its overall utility.

Proposed Feature:

• Add a parameter to the isPathValid service that allows users to define the maximum allowable cost for a path to be considered valid.

[SteveMacenski]

Seems reasonable to have a max cost parameter or in the service request itself. I think the service request having a field for the max, valid cost would be great & pretty easy contribution. @BCKSELFDRIVEWORLD can you submit a PR?