Document generated file header best practice

[cnaples79]

Summary

• add guidance to code generation docs to include a header comment noting generated files and their source template

Rationale

• issue Add Comment in Generated Code Indicating Source and Generated Status as Best Practice in Jinja Templates #440 requests a best practice to mark generated code with its source; documenting it makes templates easier to audit and discourages manual edits

Testing

• not run (docs-only change)

Fixes #440

[linux-foundation-easycla]

• ❌ - login: @cnaples79 / name: Chase Naples . The commit (6b73a3b) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[jsuereth]

@cnaples79 Would you be willing to sign our CLA?