Feat/bpi account storage prisma poc

[ognjenkurtic]

Description

From POC it turned into a full implementation of state tree leaf storage after the execution of a transaction. It relies on the previous implementation of merkle tree agent and storage agent to perform marshaling of the state tree to a text field in the DB - merkelized path pattern is not suitable for our current use case as it too complex and we can rely on state tree leaf index to store accompanying data for the leaf. Storage of this data is also implemented as part of the PR. Added a bunch of TODOs for upcoming milestone. Prisma is upgraded to version 5 as part of this PR as well.

Related Issue

702

Motivation and Context

Because having a BPI without state is like having a kafana without cigarette smoke.

How Has This Been Tested

Not tested yes. Will be tested as part of #729 with e2e tests and with unit tests as part of milestone 5 once prisma mocking is implemented.

Screenshots (if appropriate)

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Request to be added as a Code Owner/Maintainer

Checklist

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.
• [x] I commit to abide by the Responsibilities of Code Owners/Maintainers.

[Therecanbeonlyone1969]

@ognjenkurtic good to review?

[ognjenkurtic]

@ognjenkurtic good to review?

Yes now, i rebased main. @Therecanbeonlyone1969 @Kasshern @biscuitdey

[ognjenkurtic]

@Kasshern @biscuitdey addressed all the comments i think. Please rereview.