Schema field names 'id' and 'version' should be reserved

[yuvalshimron]

Describe the bug
When I define schemas with the fields "id" and "version" this seems to be accepted by the platform.
However, it generates sources which do not compile because the getters/setters of these fields collide with parent classes.

E.g. in clear() method we get:
'setId(com.yahoo.document.DocumentId)' in 'com.yahoo.document.Document' cannot be applied to '(java.lang.Long)'

And in getStructType() we get:
'getVersion()' in 'com.taboola.vespa.document.Campaign_base.Embedding_meta_data' clashes with 'getVersion()' in 'com.yahoo.document.datatypes.Struct'; attempting to use incompatible return type

To Reproduce
Create a schema with these fields:

field id type long {
  indexing: attribute | summary
  rank:filter
}

...

struct embedding_meta_data {
  field end_point_name type string {}
  field version type string {} # <------------ Here
  field update_time type long {}
}

And then generate sources.
The sources should show the compilation errors.

Vespa version
8.457.32