Improve support of stateful and stateless contracts

Currently Tealer does not have a good notion of stateful/stateless. We have some some information from the detectors
https://github.com/crytic/tealer/blob/8a7fe218a4e07b5c73f08f44516acbc0d46819ca/tealer/detectors/abstract_detector.py#L12-L15

But its not really used so far. We have to develop further the API to express better the statefullness of the contract, and make sure the proper detector are used based on that.

What we could do:
- [ ] Create statefulness information into Teal
- [ ] Create detection of the statefulness based on semantics heuristics
- [ ] Adapt existing detectors to be enabled/change their strategies based on the statefulness

Start with the statefulness information in tealer/detectors/abstract_detector.py, especially the referenced lines, and review how existing detectors use it. Define the API and semantic heuristics for identifying stateful versus stateless contracts, then adapt detectors so their availability or strategy follows that classification. Done means all three checklist areas are addressed and detector behavior reflects the contract statefulness.

Written by the indexing model from the issue text.