Permit earlier click version

[evangriffiths]

Proposed changes

Downgrade minimum click version back to 1.51.0 release version (i.e. undoing min version bump from #736)

Fixes

#736 will introduce dependency conflicts in upstream projects that depend on both https://github.com/valory-xyz/open-aea and https://github.com/valory-xyz/open-autonomy (like https://github.com/valory-xyz/mech-client) in the next release of this repo (1.52.0). This change fixes that.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have read the CONTRIBUTING doc
• I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Lint and unit tests pass locally with my changes and CI passes too
• I have added tests that prove my fix is effective or that my feature works
• I have checked that code coverage does not decrease.
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Release summary

This should be included in release 1.52.0 (for which release notes were added in https://github.com/valory-xyz/open-aea/pull/736/files)

[angrybayblade]

@evangriffiths open-autonomy and mech-client are downstream dependencies which can be updated to match the open-aea dependency versions so there won't be any breaking changes.

[evangriffiths]

@angrybayblade There would be breaking changes for any project with a dependency click==8.0.2. I can see that open-autonomy updated okay though with this new min version constraint, so that's good valory-xyz/open-autonomy@63a54d0