Python: Bump argo-client, mypy, cryptol versions

[RyanGlScott]

This patch:

• Bumps the mypy lower bounds to avoid incurring a dependency on typed-ast, which is being EOL'd soon. See typed_ast end of life (July 2023) python/typed_ast#179.
• Bumps the argo submodule to bring in the changes from Python: Avoid typed-ast dependency argo#195, which makes corresponding changes on the argo side.
• Bumps the cryptol submodule to bring in the changes from Python: Bump argo-client, mypy versions cryptol#1493, which makes the corresponding changes on the cryptol side.

[RyanGlScott]

I'm including @yav as a reviewer, since I had to selectively cherry-pick some changes from #1751 in order to bump the cryptol submodule. I think I did this the right way, but please double-check me.

[RyanGlScott]

When the CI invokes mypy, it fails with a rather baffling error that I cannot reproduce locally:

saw_client/connection.py:55: error: Assignment expressions are only supported in Python 3.8 and greater  [syntax]

The thing that baffles me is that right before this step, I specifically install Python 3.11, so I have no idea why mypy thinks it is using Python 3.8...

[kquick]

Perhaps this: https://github.com/GaloisInc/saw-script/blob/master/saw-remote-api/python/mypy.ini#L3

[RyanGlScott]

You are exactly right, @kquick. I've pushed a new version of the patch which changes mypy.ini accordingly.

Somewhat distressingly, the mypy.ini files for both argo-client and cryptol make this same mistake, but they were not caught by CI. I suppose we should update those as well...

[yav]

I think not handling DForeign and DProp in SAW for the moment is OK.

I just wonder if error is the right way to report these as I am not sure what's SAW's error reporting mechanism. We should make sure that if people use these features in a Cryptol spec and then try to use in SAW they get a normal error, rather than crashing.

[RyanGlScott]

Hah, I simply copied the error calls over from #1751 :)

Looking at the code, the existing convention appears to be that error is used for user-reachable code, e.g.,

saw-script/cryptol-saw-core/src/Verifier/SAW/Cryptol.hs

Lines 1751 to 1753 in 23cdc79

	-- functions
	TV.TVFun _aty _bty ->
	pure $ V.VFun mempty (error "exportValue: TODO functions")

And panic is used for code that is not intended to be reachable, e.g.,

saw-script/cryptol-saw-core/src/Verifier/SAW/Cryptol.hs

Line 1832 in 23cdc79

| otherwise = panic "importFirstOrderValue" ["Unexpected field name while importing finite value:", show nm]

I could be wrong in this assessment, so please speak up if I am wrong here.

[chameco]

That error-handling convention is what I'd expect (at least for existing code that isn't in MonadThrow).