Investigate schema parsing slowdown likely caused by schema annotations

[john-h-kastner-aws]

Describe the improvement you'd like to request

We recently noticed a slowdown in cedar schema parsing between versions 4.2.2 and 4.3.0. This minor version added schema annotations which required a substantial change to the cedar schema grammar, but we've not done anything yet to diagnose the exact cause of the slowdown.

We see this performance degradation across a variety of different schema which don't necessarily use scehma annotations, including the gdrive, github and tinytodo schema in the cedar-examples repository. JSON schema parsing is not significantly impacted (possibly slowing down by ~5 microseconds on some inputs, but I've not timed it precisely enough to be sure).

Describe alternatives you've considered

No response

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this internal improvement
• ⚠️ This feature might incur a breaking change

[john-h-kastner-aws]

@shaobo-he-aws investigated and now believes that the slow down is due to source information being propagated in schema types by #1406 and #1405

Not clear how to proceed. We could speed it up by applying the fast/raw parsing changes we made for policy parsing, but we actually want to revert those changes. Ideally we can find a way optimize source location propagation in both parsers without requiring conditional compilation. Alternatively, we could accept this slow down as the cost of improved error reporting.