Fix: expanded postings can cache wrong data when queries are issued "in the future"

[alanprot]

What this PR does:

See: #6556

This PR includes:

• Added unit test to catch the issue
• Improve fuzz test to add GetSeries call and run queries at a "future" timestamp
• Increase the runs from 100 to 300 on the fuzz test (even though 100 was pretty consistent to catch the issue)
• Bypass caching logic if the query is "in the future"

Additionally, we improved the prom to include all the matchers types: cortexproject/promqlsmith#142

Which issue(s) this PR fixes:
Fixes #6556

Checklist

• Tests updated
• [NA] Documentation added
• [NA] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[yeya24]

Improve fuzz test to add GetSeries call and run queries at a "future" timestamp

I don't see we added this to fuzz test?

[alanprot]

Improve fuzz test to add GetSeries call and run queries at a "future" timestamp

I don't see we added this to fuzz test?

My bad.. i added to the unit test.. lemme add some on the fuzz test as well.

We do not have expanded postings for get series for now but is good to add in case we add cache there in the future.

[alanprot]

@yeya24 Added the get series fuzzy testing.

[yeya24]

Thanks