ci: update release process with release-please

[antonbaliasnikov]

What 💻

• Add release-please configuration and workflows
• Update Docker image with cargo chef build stage that allows the proper layers caching improving docker image building time from ~30 min to ~15 min.
• Add GH attestations to Docker images as well as for binaries
• Add the capability to manually trigger binary release workflow to generate a prerelease for testing purposes
• Create only one attestation for all binaries instead of individual attestation for each binary per platform.

[dutterbutter]

@antonbaliasnikov were you able to test successfully in a fork by any chance? I suppose this will also Closes #474

[antonbaliasnikov]

@antonbaliasnikov were you able to test successfully in a fork by any chance? I suppose this will also Closes #474

@dutterbutter , I've tested it in this PR by enabling pull_request target and making sure that docker and binaries are successfully built.

In the fork, I've tested release-please as well, here is a next release PR example:
antonbaliasnikov#2
But I will test a bit more as I found see some issues with release-please tagging.

I suppose this will also Closes #474
Yes, it will. Is is aligned with the issue through the git branch name.

But we need to discuss minor details with you and @itegulov about the flow. Because release-please will always create the release first, and only then we start jobs to add binaries and publish docker images. We can re-try them if they fail, but anyway it would be nice to discuss the flow we would like to see.