feat: switch to sqlite instead of json for state persistence

[neriumrevolta]

Description

• PersistedState struct removed in favour of passing a db pool reference (&SqlitePool) wherever we need to update/query the db
• updated unit tests (they were on the state file before)
• updated e2e tests

[hopeyen]

looks good overall!

[hopeyen]

much clean!

also pls link the testing issue we discussed. I also still think cargo tests should use the sqlx::test macro, cleaner testing environment

[hopeyen]

would be good to refactor the processing here back into a similar notion of save_local_attestation(...)

[neriumrevolta]

much clean!

also pls link the testing issue we discussed. I also still think cargo tests should use the sqlx::test macro, cleaner testing environment

thanks!
I think I addressed all the comments now, I could not get sqlx::test to work even with just the cargo tests, again with the

control attributes are not allowed unless the `migrate` feature is enabled and automatic test DB management is used; see docs

Lmk if it's fine to keep it as is. Also for the е2е tests testing Issue - I am not sure how to frame the improvements we want, I think we can leave it as a separate effort from this Issue, since it's not related to the db?

[hopeyen]

I could not get sqlx::test to work even with just the cargo tests, again with the

control attributes are not allowed unless the `migrate` feature is enabled and automatic test DB management is used; see docs

I read through the docs carefully and got cargo tests to work

    #[sqlx::test(migrations = "./migrations")]
    async fn test_db_basic(pool: SqlitePool) {
        // let pool = create_test_db(None).await;
    ...
    }

If you are curious, look more carefully in the docs here talking about signatures

I still think it would be better to create the e2e test re-arch issue and link it here, because the changes in the e2e tests right now is not the ideal which leads to the motivation for that spec'ing work. feel free to leave it a bit more general and fill in later. Some main points are to talk about why there are multiple test binaries and a separate db testing management, what was the limitations of having them within the radio crate, and some functions to be moved into the SDK

Other changes look okay

[hopeyen]

🤞!

[neriumrevolta]

@hopeyen I will link the testing Issue later today