feat: add detector for unused custom errors

[gvladika]

New detector looks for Solidity custom errors which are declared, but never used. This can indicate a mistake, ie. error is declared but check which would invoke the error was never put in place.

It can be executed like this:

slither .  --detect unused-custom-errors

Output will list identified unused errors and the respective file names. Ie.

The following unused error(s) should be removed:
        -UnusedLibError() (tests/e2e/detectors/test_data/unused-custom-errors/0.8.15/CustomErrorsLib.sol)

        -UnusedErrorLibConsumerErr() (tests/e2e/detectors/test_data/unused-custom-errors/0.8.15/ErrorLibConsumer.sol)

        -UnusedParentErrWithArg(uint256) (tests/e2e/detectors/test_data/unused-custom-errors/0.8.15/ContractToTestForCustomErrors.sol)

        -UnusedParentErr() (tests/e2e/detectors/test_data/unused-custom-errors/0.8.15/ContractToTestForCustomErrors.sol)

        -UnusedTopLevelErr() (tests/e2e/detectors/test_data/unused-custom-errors/0.8.15/ContractToTestForCustomErrors.sol)

[CLAassistant]

All committers have signed the CLA.

[smonicas]

Checking the name could have false negative. For example try adding this in the contract test. It won't get detected.

contract C {
    error UsedParentErr(address x);
}

A better approach could be to have custom_errors with the actual CustomError instance instead of the name and then check here with declared_error == custom_revert. When you are adding the custom error you can get the instance with internal_call.function.custom_error

[smonicas]

You can just use custom_error and in the output you will have automatically its filename. Also it would be better to have individual findings for each custom error instead of one with everything.