anchor.diff:  because the `@picocli.groovy.PicocliScript` annotation class and supporting classes have been moved into a separate module, `picocli-groovy`.
   
   ==== Closures in Annotations
  -From picocli 4.6, Groovy programs can use closures in the picocli annotations instead of specifying a class.
  +As of picocli 4.6, Groovy programs can use closures in the picocli annotations instead of specifying a class.
   This can be especially useful in Groovy scripts, where one cannot define a static inner class.
   
   Example:
  
positive.code: [grid=cols,cols=3*,options="header"]
  |===
  | | `IParameterPreprocessor` | `IParameterConsumer`
  | *Functionality* | Either augment (return `false`) or replace (return `true`) picocli parsing logic for the matched element. | Replaces picocli parsing logic for the matched element.
  | *Scope* | Commands as well as options and positional parameters. | Options and positional parameters only.
  | *Information on parser internal state* | Yes, information may received via the `info` Map | No
  | *Communication back to parser* | Yes, via modifying the `info` Map | No
  
negative.code: 
  === Show At Files
  
  As of picocli 4.2, an entry for `@<filename>` can be shown in the options and parameters list of the usage help message of a command with the `@Command(showAtFileInUsageHelp = true)` annotation.
  
  ==== Example
  
  