feat(plugins): adds testnet address for unruggable

[ZackAttax]

No description provided.

[antiyro]

could you rather implement a specific config for unruggable agents under config/agents/unruggable.agent.json

[ZackAttax]

I was using this config for manual testing but sure

[antiyro]

could you keep an exemple value here like YOUR_STARKNET_NETWORK

[antiyro]

@ZackAttax Actually, I’m not sure if relying on an environment variable for the network is the right solution since "mainnet" could be defined as:

• "mainnet"
• "SN_MAIN"
• "0x534e5f4d41494e"

Each plugin could define it in its own way if we don’t enforce a standard. But the problem is that limiting it to just "mainnet" and "testnet," for example, would break compatibility with App Chains.

One possible solution to ensure a unique source of truth would be for getNetwork to store once provider.chainId, which should return option 3, "0x534e5f4d41494e," for mainnet. This can then be interpreted as option 2, "SN_MAIN".
In the case of App Chains, it would work out of the box.

Users would then have to implement it as follows:

export const getNetworkFactoryAddress = (agent: StarknetAgentInterface) => {
  const network = agent.getNetwork();
  return network === 'SN_MAIN'
    ? FACTORY_ADDRESS_MAINNET
    : FACTORY_ADDRESS_TESTNET;
};

The only cons is that it is a bit more low level for users and devs but way more exportable accross all networks.