chore(parser): pin shared PromQL parser revision

[milindsrivastava1997]

Why

The shared parser fork now includes the reviewed v0.10 parser fixes and recognizes distinct_over_time and entropy_over_time. Planner must use the same immutable revision as backend parsing.

What

Pin asap-frontend-promql to ProjectASAP/promql-parser commit d7606436bde05efe19c5398fe2122faa49062f7d and refresh the lockfile.

How

The frontend keeps ownership of PromQL lowering. The parser dependency only expands accepted syntax; functions receive acceleration semantics only through an explicit lowerer mapping.

Before this PR

Planner resolved the older fork revision c51beafb.

After this PR

Planner resolves v0.10 from d7606436. distinct_over_time and entropy_over_time parse but remain exact-only because the lowerer rejects them. topk_over_time remains outside the parser contract.

Verification

• cargo check -p asap-frontend-promql
• Boundary test proves distinct_over_time and entropy_over_time parse and then fail lowering with UnsupportedFunction.
• cargo tree -p asap-frontend-promql resolves only d7606436.
• cargo fmt -p asap-frontend-promql -- --check
• git diff --check

Limitations

This PR does not add lowering, planning, or runtime support for the newly parsed MetricsQL reducers.