(WIP-DO-NOT-MERGE) feat: Support-for: 3.12/3.13

[8ball030]

trafficstars

Proposed changes

Basically i am little blocked on support for 3.13.

This seems to be caused by a couple of issues.

A) abci relies on grpcio 1.53.0 This fails with a compilation error in python 3.12 when trying to build the wheel. By bumping to 1.71.0 we should solve this.

B) tomte/flake8 Unfortunately, flake8 is needed for tox etc which conflicts with the grpcio when trying to bump as in this pr https://github.com/valory-xyz/tomte/pull/29

C) Open-aea-cosmpy which is causing the failing ci. Upstream however has the solution to get 3.12 working.

Could we please create this pr as I am unable to do so;

Fixes

If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.) Put an x in the box that applies

• [x] Non-breaking fix (non-breaking change which fixes an issue)
• [ ] Breaking fix (breaking change which fixes an issue)
• [ ] Non-breaking feature (non-breaking change which adds functionality)
• [ ] Breaking feature (breaking change which adds functionality)
• [ ] Refactor (non-breaking change which changes implementation)
• [ ] Messy (mixture of the above - requires explanation!)

Checklist

Put an x in the boxes that apply.

• [ ] I have read the CONTRIBUTING doc
• [x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
• [ ] Lint and unit tests pass locally with my changes
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ x] I have locally run services that could be impacted and they do not present failures derived from my changes
• [ ] Public-facing documentation has been updated with the changes affected by this PR. Even if the provided contents are not in their final form, all significant information must be included.
• [ ] Any backwards-incompatible/breaking change has been clearly documented in the upgrading document.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...