Add Configuration Version and Validation Function

[cryi]

Based on discussions and the dismissal of #516, we agreed on moving forward with templating. To support this, we could use a version field and a validation function to ensure compatibility.

Would it be possible to include a configuration version and a simple validation function to check the version against the signatory binary? This would provide an easy way to automate configuration generation for tools that depend on signatory.