[FEATURE] add extract fields transform to cue

[shahrokni]

Description 🖊️

This change will add the extract fields transform definition to cue.

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.
• E2E tests are stable and unlikely to be flaky.
  See e2e docs for more details. Common issues include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.

[jgbernalp]

LGTM, But I'll let @AntoineThebaud to also check

[jgbernalp]

@shahrokni are there any test we can make for this changes?

[shahrokni]

@shahrokni are there any test we can make for this changes?

I am not sure how we could only test the cue schema change. Is there any way that I am not aware of?

[AntoineThebaud]

@shahrokni are there any test we can make for this changes?

I am not sure how we could only test the cue schema change. Is there any way that I am not aware of?

yes we have a basic testing framework in place for these common CUE definitions, see

• https://github.com/perses/shared/blob/main/scripts/test-cue/test-cue.go#L25-L26
• https://github.com/perses/shared/tree/main/cue-test