Refactor `gnosis_safe_proxy_factory` -> `gnosis_safe_multisig`

[jmoreira-valory]

Refactor gnosis_safe_proxy_factory -> gnosis_safe_multisig

gnosis_safe_proxy_factory is a very bad name choice. Gnosis safe proxy factory is a native Safe contract, whereas ours is called GnosisSafeMultisig.

This fix would imply renaming associated variables used in the protocol deploy method. In particular this will introduce at least a breaking change by renaming the environment variable

CUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS --> CUSTOM_GNOSIS_SAFE_MULTISIG_ADDRESS

Update

There is a contract package gnosis_safe_proxy_factory which refers to the actual proxy factory. There is a mixture of usage in the library of the concept gnosis_safe_proxy_factory (when it's correctly referenced as the Gnosis factory) and gnosis_safe_proxy_factory, when it's incorrectly referenced as the (Olas) gnosis_safe_multisig from the autonolas-registries repository.

[jmoreira-valory]

See also:
valory-xyz/olas-operate-app#643
https://github.com/valory-xyz/olas-operate-app/pull/258/files#r1702118215

[DavidMinarsch]

Still relevant. The misnaming persists across the codebase:

• autonomy/chain/constants.py:46-190 — every chain config has a "gnosis_safe_proxy_factory" field with trailing comment # Multisig WITHOUT recovery module, confirming each address is actually the Olas GnosisSafeMultisig, not the Safe-native proxy factory.
• autonomy/chain/config.py:428-431 — the ContractConfigs field is also called gnosis_safe_proxy_factory.
• autonomy/chain/service.py:535-536 — demonstrates the confusion: assigns to a correctly-named local gnosis_safe_multisig by looking up GNOSIS_SAFE_PROXY_FACTORY_CONTRACT.name.

Note there is also a legitimate packages/valory/contracts/gnosis_safe_proxy_factory/ package for the real Safe-native proxy factory — that should stay.

A proper fix would need to:

1. Rename the JSON field / ContractConfigs attribute / constant name from gnosis_safe_proxy_factory → gnosis_safe_multisig.
2. Rename the env var CUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS → CUSTOM_GNOSIS_SAFE_MULTISIG_ADDRESS (breaking change — downstream middleware/trader read these).
3. Keep the real gnosis_safe_proxy_factory contract package unchanged.
4. Either add backwards-compat aliases for the env var (preferred, for downstream migration window) or coordinate a simultaneous bump in middleware + trader.

Keeping open — non-trivial refactor with breaking-change coordination needed.