feat(storage): allow record in watch callback

[dvlden]

🔗 Linked issue

#341

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

It provides flexibility in what the watch callback can return, when changes are detected.
Sometimes it can be highly useful to get both the key and the value of the property that was changed. I guess sometimes it can be used for some additional properties too.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

I did not find in the docs any mentions of what callback must be defined as.

[pi0]

Hi. I appreciate your work on this PR mostly non of storage driver watchers get the value on watch event nor this PR adds support for any driver.

We can do it by introducing a third optional value?: unknown parameter to the callback AND consider which drivers already have it in their watch event (I guess currently only web-based drivers)

Closing PR but feel free to open a new with above proposal.