Add targeted cross-property integrity checks / warnings

There are at least a few properties whose validity and/or effect depends on both their own values **and** the value of one or more other properties. For example,
- It doesn't make sense to set `tss.historyEnabled=true` unless `tss.hintsEnabled=true`, because only then do we have a hinTS verification key that _needs_ a history proof,
- It doesn't make sense to set `tss.wrapsEnabled=true` unless `tss.historyEnabled=true`, because a WRAPS proof is a special type of history proof.

➡️ Although one could easily take such considerations too far, it's probably useful in at least a few cases like these to log at `WARN` when a node starts with an inconsistent property configuration.

No file, test, or entry point is identified in the issue. Review startup configuration handling for tss.hintsEnabled, tss.historyEnabled, and tss.wrapsEnabled; done means inconsistent combinations log WARN messages without changing valid configurations.

Written by the indexing model from the issue text.