chore: Add template milestone 3 updates

[CodeMonkeyF5]

Proposed changes

Config Templates — UI screens, submission persistence, and template management

New files

• template-detail-view.md — Documents the Template Detail page (Details tab): field descriptions, tmpl_ vs tmplv_ identifier guidance, and API reference.
• template-versions.md — Documents the Versions tab: data grid columns, delete constraints, and API references.
• template-submissions-view.md — Documents the Submissions view (Details tab): data grid columns and delete action.

Updated files

• one.json — Latest regenerated with x-nodoc removed for templates m3 APIs
• author-templates.md — Updated "Template Submission" glossary entry; added "Static include files" subsection documenting file_type: include; removed outdated external-file limitations; added "Template lifecycle management" section covering updateTemplateMetadata, patchTemplateMetadata (with draft→final irreversibility callout), and copyTemplate.
• import-templates.md — Updated archive structure to support static include files; updated tips section restoring the "avoid hidden/backup files" example (with .conf/.types in the correct example) and added a new tip for bundling include files.
• submit-templates.md — Removed "Current Limitations" section; split request into submission mode (preview_only=false, default) and preview mode (preview_only=true); added current limitation callout (targets limited to staged configs); added "Manage template submissions" section covering getTemplateSubmission, updateTemplateSubmission, updateSingleTemplateSubmission, and deleteTemplateSubmission.
• save-as-staged-config.md — Reframed: direct submission is now the recommended approach; preview-then-manual-create retained as the alternative workflow.
• add-multiple-services.md — Updated stale callout to reflect that submissions are now persistent and retrievable.

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 Technical Writing Style Guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[CodeMonkeyF5]

I have hereby read the F5 CLA and agree to its terms

[syousF5]

I left one comment.