[False-Positive]: Function marked as re-entrant

### Describe the false alarm that Slither raise and how you know it's inaccurate:

I have a function F in contract A, that can only be called from contract B.
Slither marks some lines of F as possible re-entrant, while this is not possible.

Is it possible to disable the check for the whole function, or do I have to add `//slither-disable-next-line reentrancy-no-eth` over every re-entrant line?

### Frequency

Occasionally

### Code example to reproduce the issue:

```Solidity
modifier onlyOtherContract () {
require(msg.sender == otherContract, "Only otherContract can call this");
_;
}

function F() external onlyOtherContract {
...
bool successfulApproval = _token.approve(address(_gToken), _amount); // <<-- one of the lines that is marked as possibly re-entrant
...
}
```

### Version:

I use it in a github action, with `crytic/slither-action@v0.3.0`

### Relevant log output:

_No response_

Reproduce the report with the Solidity modifier and function example using the reentrancy-no-eth detector, starting from the suppression behavior exposed by the Slither CLI or GitHub Action. Trace how next-line suppression is applied and determine whether function-level suppression is supported; done means the requested scope works consistently or the documented limitation is clear.

Written by the indexing model from the issue text.