feat(x/params): add lru caching

[moul]

LRU caching uses a specified CacheMaxSize to limit the number of entries. Keys are immediately invalidated when a setter is called. The LRU is shared across all the getters.

Fix #3023
Related with #2911

[codecov]

Codecov Report

Attention: Patch coverage is 70.83333% with 7 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
tm2/pkg/sdk/params/keeper.go	75.00%	3 Missing and 1 partial ⚠️
gno.land/pkg/gnoland/node_inmemory.go	0.00%	2 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[ajnavarro]

What are the performance gains of this PR? K/V storages usually have cache mechanisms like the one implemented here, so maybe it is redundant?

[ajnavarro]

Maybe this lib is more maintained than the one used: https://github.com/hashicorp/golang-lru

[ajnavarro]

what is the meaning of that code? can we have nil values in our cache? why?

[moul]

I was considering the two situations, and I feel that since the goal is to avoid unnecessary lookups, caching the "not found" error prevents a misconfigured script from periodically querying the same nonexistent value for a real lookup.

It's just a feeling; I'm not sure if that's the best approach.

[ajnavarro]

we can use bloom filters for that specific case if we receive a lot of queries for data we don't have.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: moul/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[thehowl]

This PR is a bit old, and I know there's other developments on the params module. @moul, tell me if you want me to take a look or I can hold off the review for the moment.