Tie peg parser generation into the dev server optimization

[Bargs]

The kuery grammar gets precompiled and committed to git now, which means in dev you need to run grunt peg or grunt watch:peg to see your changes to .peg files. It would be really nice if these files were watched and compiled as a part of the usual optimization process.

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[lukeelmers]

Whatever solution we use for this should probably be consistent in the expressions plugin too (which also uses peg)

[tylersmalley]

@lukeelmers this is on my radar as I have opened #85341 to remove Grunt, which is used by kquery. Think we can move this to a package?

[lukeelmers]

@tylersmalley Yeah this is potentially something we could extract to a package, along with a few other pieces of es_query that have been problematic for different reasons (like circular dependencies & a core -> data dependency we need to remove).

I will bring this up so we can have it on the app services roadmap. Do you have a target release in mind for removing grunt?

[jbudz]

Hey @lukeelmers - we're targeting 7.12 for Grunt removal currently. I'm happy to help if there's any bandwidth issues.