Add x-auditable information to common.yaml schemas

[arispoloway]

A number of teams reference these schemas internally (particularly uuid and identifier), and it's somewhat challenging to add information about auditability without updating all of those references.

I left off user information aside from username and email, but basically everything else here should be fine to audit.

[kodster28]

Heyo, looks like this has the same problem as #27

(this is a read-only public repo)

[arispoloway]

I thought just the openapi.(yaml|json) files were updated automatically? I saw #21 as the last update to this file, so I figured we were supposed to update it here

[kodster28]

Oh, maybe!

@jacobbednarz would know!

[jacobbednarz]

we're having a somewhat related conversation internally about these common components as we're looking to limit the amount of reuse we have in the schemas. it's causing modelling issues due to people blindly copy/pasta components and making the documentation and SDKs harder to debug. depending on how urgent this is, i'd hold off in case we remove this in favour of something else.

[arispoloway]

Gotcha - the reuse has been annoying for us as well - until teams actually stop using the references, there's not really a way for us to mark those fields as auditable beyond updating the referenced components.

I'm happy to hold off for a little bit while y'all settle on a direction here, but I just want to make sure that eventually the teams referencing these components (identifier and uuid especially) have those fields marked as auditable, whether that be through a change here, or replacing all the references, or something else.