Pipeline behaviors applied to every command and query execution.
Behaviors are invoked in declared order. Each behavior receives the
request and a next() function; returning without calling next()
short-circuits the pipeline (the handler and later behaviors do not run).
An entry is either a behavior instance or a factory that builds one from
the service registry. At the onInit phase the WHOLE list is resolved in
declared order and installed on both buses, so a mixed list runs in
declared order — not instances-then-factories.
Default: [] (no behaviors).
readonly (IPipelineBehavior | RegistryFactory<IPipelineBehavior>)[]