CLI: "pattern" and "replacement" should be required when creating logging filter

It's able to set filter attribute without "pattern" and "replacement" although they are not nillable.

calling:
/subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value={replace => {"replace-all" => true}})

will create useless filter:
"filter" => {"replace" =>

{ "replace-all" => true, "pattern" => "undefined", "replacement" => "undefined" }}

"filter-spec" => "substituteAll(\"undefined\",\"undefined\")"

only "replace-all" is actually required now:
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:update-properties(filter={replace => {"pattern" => "JBAS","replacement" => "SABJ"}})
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: null",
"rolled-back" => true
}