### TL;DR
Simplified the auto-release workflow by utilizing a reusable workflow from init4tech/actions.

### What changed?
Replaced the custom release verification and creation logic with a standardized reusable workflow. The new workflow maintains the same trigger conditions (pushing to main branch with changes to Cargo.toml) while reducing complexity.

### How to test?
1. Update the version in Cargo.toml
2. Push changes to the main branch
3. Verify that a new release is automatically created with the updated version

* WIP: adding bundle fetcher support

* WIP: separating auth out into authenticator

* WIP: fixing the cannot drop a runtime in a blocking context error

* WIP: Fixes tokio runtime drop bug

* wip: cleanup and remove imports

* chore: fix dep error

* chore: mark bundle poller test as it

* feat: spawn bundle poller and handle exits

* feat: ingest bundle transactions, drop bundle on failure

This implements ingesting bundle transactions naively. It does not take into account the bundle "rules", so to say, which would make it a bit more complex. If a transaction fails to decode, the bundle is considered "invalid", and dropped.

* chore: clippy

* chore: comments

* chore: clarify comment on signed orders

* chore: dedup oauth, do not use spawn blocking

* chore: remove unneeded async

* chore: clean up authenticator

* feat: track seen bundles to dedup

* feat(`oauth`): caching, shareable authenticator (#19)

* feat: caching, shareable authenticator

* fix: actually spawn builder task lmao

* chore: remove unnecesary mut selfs

---------

Co-authored-by: evalir <e@evalir.xyz>