Feat/adding memory layer

[doriwal]

Description

Brief description of the changes in this PR.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Maintenance/refactoring
• ⚡ Performance improvement
• 🧪 Test improvement

Testing

• Tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

Related Issues

Closes #(issue number)

Screenshots (if applicable)

Additional Notes

Any additional information that reviewers should know.

[OtherVibes]

I'd prefer to limit by record count and not by date with FIFO strategy

[doriwal]

There are 2 clean logic

1. remain only X records and when x+1 msg arrive we remove first item and add new one in the end
2. daily cleanup as in memory storage does not clean when session ends - we dont know when it ends