🐛 fix issue on RiskStewards contract name for same chain pools

[MartinGbz]

Issue: the generator doesn't use the right RiskStewards contract name on the file it generates. It uses the chain name instead of the pool name. So pools like Lido or Etherfi use the same RiskStewardsEthereum instead of their own.
This leads to the execution of calldatas that return errors because they are simulated on the wrong RiskStewards address.

Instead of getting the chain name to compute the RiskStewards contract name, we now use the suffix of Pool names.
So: AaveV3EthereumLido => EthereumLido

Tested locally contract on Core and Prime pool: ✅