include {default,local}.meta configs
add a few more data types: numbers (including relative times), strings
missed "s" in highlight group name, and a missing *Stanzas
start moving *Stanzas to syn-match for better control; starting with alertaction
app.conf update; include string after credential:
audit.conf update; also include eventSigning
authentication.conf update; include complex stanza and a few keywords (admin,
etc)
authorize.conf update; complex stanzas and add missing keyword
commands.conf update

The Stanzas update is really to follow the pattern. The syn case changes are to
account in a difference between the .spec and the .example -- one uses all caps
while the other uses all lowcap.
crawl.conf update; add missing network stanza
datamodels.conf, default-mode.conf, deploymentclient.conf updates

Pretty standard -- default-mode.conf Stanzas gets its complex value
distsearch.conf update; complex stanzas and a missing keyword
event*.conf, fields.conf updates
indexes.conf update; complex stanza and added some constants
inputs.conf updates; lots of complex stanzas
limits.conf updates
multikv.conf updates; missing keywords

This one was almost completely broken. The replacement regex matches all of the
complex keywords
outputs.conf, pdf_server.conf updates
props.conf, serverclass.conf updates; complex stanzas and keywords

confComplex keywords are highlighted differently since they need to be globally
unique (props.conf) or in a sequence (serverclass.conf)
pubsub.conf, regmon-filters.conf, restmap.conf, savedsearches.conf updates