docs: Chainstack implementation update

[soos3d]

What I did

• Updated repo URL in setup.py to https://github.com/ApeWorX/ape-chainstack
• Removed Kovan from providers.py as it's not supported by Chainstack
• Updated README.md

Checklist

• [x ] Passes all linting checks (pre-commit and CI jobs)
• [ x] New test cases have been added and are passing
• [ x] Documentation has been updated
• [ x] PR title follows Conventional Commit standard (will be automatically included in the changelog)

[soos3d]

This time should not have conflict as I re-forked the repo with your updates (I only removed Kovan because is not supported by Chainstack)

[NotPeopling2day]

Looks good! Quick recommendation is to change reference to the Ape Framework vs ApeWorX the organization.

[antazoey]

Looking good!
Consider my feedback on the networks list thought

[antazoey]

Consider an explanation instead of enumerating all the options here. Something like:

You compose the network option by following this formula: <ecosystem>:<network>:<provider> where "chainstack" is the provider.
See the full output of networks in your ape instance by using the command `ape networks list`.
For more information on networking un ape, see [this guide (https://docs.apeworx.io/ape/stable/userguides/networks.html).

Let's say we increase support for new networks in chainstack; this list will become outdated. I am trying to avoid someone having to keep this documentation up to date as the plugin grows.

[antazoey]

Linking to this doc is probably sufficient https://docs.apeworx.io/ape/stable/userguides/networks.html

[soos3d]

true, you can go ahead and propose the change if you can, it's probably quicker like that than if I change it later

[soos3d]

I actually updated it in on my side. What is a good way to implement it here now?

[NotPeopling2day]

Thank you so much!