feat!: diamond config change + cleanup legacy [CHAIN-682]

[justprosh]

Description

• simplify chain config re Diamond contract upgrade: diamond_contract_address instead of core_contract_address, cc_contract_address and market_contract_address
• remove Subnet.resolve with legacy chain-parsing code and implement in connector
• remove unused decider config fields: network_api_endpoint, network_id, matcher_address, start_block, worker_gas, wallet_key
• renamed pat_id field to cu_ids and changed type to vec (re multi CC update) in ResolveSubnetResult (fixed in feat!: change Worker type in SubnetResolveResult aqua-lib#88)
• remove legacy system services envs: FLUENCE_ENV_AQUA_IPFS_EXTERNAL_API_MULTIADDR, FLUENCE_ENV_AQUA_IPFS_LOCAL_API_MULTIADDR, FLUENCE_ENV_CONNECTOR_JOIN_ALL_DEALS, FLUENCE_ENV_CONNECTOR_API_ENDPOINT, FLUENCE_ENV_CONNECTOR_CONTRACT_ADDRESS, FLUENCE_ENV_CONNECTOR_FROM_BLOCK, FLUENCE_ENV_CONNECTOR_WALLET_KEY, FLUENCE_ENV_DECIDER_IPFS_MULTIADDR, FLUENCE_ENV_CONNECTOR_WORKER_GAS

Config changes

Before:

# ...
[system_services.decider]
  decider_period_sec = 30
  worker_period_sec = 30
  worker_ipfs_multiaddr = "/dns4/ipfs.fluence.dev/tcp/5001"
  network_api_endpoint = "rpc.stage.fluence.dev"
  network_id = 123
  matcher_address = "addr1"
  start_block = "latest"
  worker_gas = 1
  wallet_key = "key"

[chain_config]
  http_endpoint = "rpc.stage.fluence.dev"
  core_contract_address = "addr3"
  cc_contract_address = "addr2"
  market_contract_address = "addr1"
  network_id = 123
  wallet_key = "key"
  # ...

After:

# ...
[system_services.decider]
  decider_period_sec = 30
  worker_period_sec = 30
  worker_ipfs_multiaddr = "/dns4/ipfs.fluence.dev/tcp/5001"

[chain_config]
  http_endpoint = "rpc.stage.fluence.dev"
  diamond_contract_address = "addr"
  network_id = 123
  wallet_key = "key"
  # ...

Checklist

• The code follows the project's coding conventions and style guidelines.
• All tests related to the changes have passed successfully.
• Documentation has been updated to reflect the changes (if applicable).
• All new and existing unit tests have passed.
• I have self-reviewed my code and ensured its quality.
• I have added/updated necessary comments to aid understanding.

Reviewer Checklist

• Code has been reviewed for quality and adherence to guidelines.
• Tests have been reviewed and are sufficient to validate the changes.
• Documentation has been reviewed and is up to date.
• Any questions or concerns have been addressed.

[linear]

CHAIN-682 Change nox chain config re diamond

[folex]

I didn't quite get the tests changes, otherwise LGTM