Adding scope_distace config for hunt module

[Giardi77]

Problem: The hunt module generates findings for out-of-scope targets (e.g., distance > 0) , even when the scan is intended for distance 0 targets due to the default scope_distance_modifier, causing it to generate a lot of noise like:

[FINDING]               {"description": "Found potential SERVER-SIDE TEMPLATE INJECTION parameter [id]", "host": "www.googletagmanager.com", "url": "https://www.googletagmanager.com/gtag/js"}       hunt    (distance-1)

Solution: Make hunt module's scope_distance_modifier configurable. This allows restricting hunt to operate only on distance 0 targets by setting scope_distance in its configuration.

ps: I don't know if this is the right way to approach the problem but this tool is amazing and i wanted to try and contribute with something little.

[TheTechromancer]

The bug in this situation is that WEB_PARAMETER events are being raised for out of scope assets. This shouldn't be happening.

@liquidsec