Use z3-solver python package instead of z3 binaries

[r0qs]

Image builds for #16199

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2404.clang-6 [solbuildpackpusher/solidity-buildpack-deps@sha256:55c26efa5e74cff46f424396c21d5614531f8043c552e27d1c7277bc7d39db9b].

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2404-5 [solbuildpackpusher/solidity-buildpack-deps@sha256:978a3735643b310e2d18195c8e9b3e317fac995866eb6ed6d066fa8387dcd0e5].

[matheusaaguiar]

Aren't we dropping ubuntu 22.04?

[cameel]

We are: #16251.

[r0qs]

Aren't we dropping ubuntu 22.04?

Yes. I noticed that we forgot to remove the 22.04 files because of this PR ;)

Note, I skipped the last buildpackdeps builds because the images were already correctly built.

[nikola-matic]

Aren't we dropping ubuntu 22.04?

Yes. I noticed that we forgot to remove the 22.04 files because of this PR ;)

Note, I skipped the last buildpackdeps builds because the images were already correctly built.

Does it matter that they were correctly built previously (I see the hashes)? If you push, you should let the build run regardless - this way it looks like the CI job on the PR has failed.

[r0qs]

Aren't we dropping ubuntu 22.04?

Yes. I noticed that we forgot to remove the 22.04 files because of this PR ;)
Note, I skipped the last buildpackdeps builds because the images were already correctly built.

Does it matter that they were correctly built previously (I see the hashes)? If you push, you should let the build run regardless - this way it looks like the CI job on the PR has failed.

I mean, if I push it will generate new hashes and yes, it doesn't matter as far as we are using the hashes that represent the latest correct change. Anyway, I triggered a re-run now.

[nikola-matic]

Aren't we dropping ubuntu 22.04?

Yes. I noticed that we forgot to remove the 22.04 files because of this PR ;)
Note, I skipped the last buildpackdeps builds because the images were already correctly built.

Does it matter that they were correctly built previously (I see the hashes)? If you push, you should let the build run regardless - this way it looks like the CI job on the PR has failed.

I mean, if I push it will generate new hashes and yes, it doesn't matter as far as we are using the hashes that represent the latest correct change. Anyway, I triggered a re-run now.

Thanks for the rebuild <3

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2404-5 [solbuildpackpusher/solidity-buildpack-deps@sha256:6eb911972a4335c21fd7725160374acf12158cc872c9215b46b335834c7dce63].

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2404.clang-6 [solbuildpackpusher/solidity-buildpack-deps@sha256:485aab7c182f167a8d7ab2b06155c4cc77138c57c8d40261946d65ee74fd0f68].