[feature]: create a `strict` mode for pipeline configuration parsing

[steven-terrana]

Feature Description

currently, when a Pipeline Configuration overrides a field it is not allowed to, this is ignored.

propose adding a

jte{
  strict_configuration_overriding = false // default is true 
}

when strict_configuration_overriding is true, the pipeline will fail in the case of:

block{
  field = "something"
}

block{
  field = "something else" // not permitted
}

[cokieffebah]

after reading #300, I see the value. maybe just strict_configuration because it has to apply to @merge also