Fix RabbitMQ detector not respecting timeout

[rgmz]

Description:

This adds a timeout to the RabbitMQ detector.

2024-10-15T18:28:56-04:00	error	trufflehog	a detector ignored the context timeout	{"detector_worker_id": "4ZclX", "detector": {"type":"RabbitMQ"}, "timeout": 10}

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

[rgmz]

Future work would be to categorize the errors provided by this, differentiating between valid and invalid.

Such as:
Verification issue: lookup xcws0001: no such host
Verification issue: i/o timeout

[abmussani]

@rgmz thanks for the fix. Instead of 10s constant timeout, Will it be a good idea to calculate the remaining time using context.Deadline() ? and use default 10s if there is no deadline define ?

[rgmz]

Will it be a good idea to calculate the remaining time using context.Deadline() ? and use default 10s if there is no deadline define ?

I think that risks exacerbating #2991.

IMO, the problem is detectors taking an unreasonable amount of time or hanging. If something needs a bit more time than the deadline to be verified, I think that's acceptable.