fix: issue with networks context when networks shared chain ID

[antazoey]

What I did

Found a weird thing in the networks context manager where would use wrong previously connected provider if two networks shared the same chain ID. In the case for ape-starknet, both testnet and local share the same chain ID for whatever reason. Theoretically though any local network can have any same chain ID.

How I did it

Use full ID pattern of <ecosystem_name>:<network_name>:<provider_name>-<chain_id>

How to verify it

Changing network but not changing chain ID should use different provider instances in the provider context manager.

(alien) ➜  ape git:(ever) ape console --network starknet:local
INFO: Starting 'starknet-devnet' process.

In [1]: id0 = id(provider)
In [2]: with networks.parse_network_choice("starknet:testnet") as provider:
   ...:     id1 = id(provider)
   ...: 
In [3]: id0 != id1
Out[3]: True

This is False on main

Checklist

• All changes are completed
• New test cases have been added
• Documentation has been updated

[sabotagebeats]

Reviewed demo by @unparalleled-js
reapproving as previously approved by @fubuloubu