Fix the e2e tests failure due to "Blacklistable: account is blacklisted"

[PaulRBerg]

USDC has a built-in black listing mechanism, and once every so often our end-to-end tests fails because of this revert reason:

Blacklistable: account is blacklisted

What happens is that Foundry fuzzes a user that has been blacklisted. We should exclude this edge case and do not fail the tests.

[PaulRBerg]

UPDATE: I tried implementing this, but this ain't easy, in the sense that we would have to add quite a a bit of logic to our end-to-end tests.

Foundry doesn't have a way to ignore certain revert reason strings, so the only way to ignore them would be to use the try/catch in all calls to the linear and the pro contracts (USDC checks that both the sender and the recipient are not blacklisted, see lines 837 and 837 here). That would make the e2e tests even complicated than they already are.

Therefore, given these constraints, I will proceed with closing this issue as not planned.

[PaulRBerg]

FWIW, I have just created an issue in the Foundry repo to suggest the addition of a new feature that would make for a better UX here.

foundry-rs/foundry#4271

[PaulRBerg]

Going to reopen this issue because we keep bumping into the blacklistable error in our CI end-to-end tests:

https://github.com/sablierhq/v2-core/actions/runs/4187172153/jobs/7256695965