ref: #84

This PR adds a new reload field to profiles that allows users to filter reload events using CEL expressions:

profiles:
  helm:
    command: helm
    args: [template, .]
    source: >-
      files.filter(f, pathExt(f) in [".yaml", ".yml", ".tpl"])
    reload: >-
      fs.event.has(fs.WRITE) &&
      render.stage < render.STAGE_POST_RENDER &&
      render.result != render.RESULT_CANCEL

If no reload expression is provided, profiles will continue to work as before (reloading on all events). Note: existing path functions are also available.

New CEL EnvOptions

New CEL functions and constants are available for these expressions.

File System Variables:

• file - The subject of the event.
• fs.event - The triggering file system event.

File System Functions:

• has(event, flag...): Check if file system events contain specific flags

File System Constants:

• fs.CREATE, fs.WRITE, fs.REMOVE, fs.RENAME, fs.CHMOD: Event type constants

Render Status Variables:

• render.stage - The current render stage.
• render.result - The last render result.

Render Status Constants:

• render.STAGE_*: Track current render stage (NONE, PRE_RENDER, RENDER, POST_RENDER)
• render.RESULT_*: Track last render result (NONE, OK, ERROR, CANCEL)

Example Use Cases

# Skip reloads for certain files
reload: >-
  pathBase(file) != "kustomization.yaml"

# Only reload on write events
reload: >-
  fs.event.has(fs.WRITE)

# Prevent reloads during active rendering
reload: >-
  render.stage < render.STAGE_RENDER

# Skip reloads if last operation was canceled
reload: >-
  render.result != render.RESULT_CANCEL