Track original config resources in SDS

Currently SDS stores various pieces of the original config, e.g. TLS certificates, as distinct objects. This makes assembling a config dump challenging, in particular when we have cross v2/v3 versioning concerns. We should probably switch to just storing the SDS resource that was delivered on the wire (with redaction).