BanyanDB: fix when setting @BanyanDB.TimestampColumn, the column should not be indexed.

[wankai123]

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
• Update the CHANGES log.

[Copilot]

Pull Request Overview

This PR fixes a BanyanDB indexing issue where columns marked with @BanyanDB.TimestampColumn should not be indexed. The fix ensures that timestamp columns are properly excluded from index creation in BanyanDB while removing redundant @BanyanDB.NoIndexing annotations.

• Updated MetadataRegistry to check if timestamp columns should be indexed before creating index rules
• Removed @BanyanDB.NoIndexing annotations from timestamp fields across multiple record classes
• Fixed error messages and improved documentation for timestamp column behavior

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
MetadataRegistry.java	Added logic to prevent indexing timestamp columns in trace and measure models
StorageModels.java	Fixed error message typo for missing TraceIdColumn annotation
Multiple Record classes	Removed redundant @BanyanDB.NoIndexing annotations from timestamp fields
BanyanDB.java	Updated documentation to clarify timestamp column indexing behavior
ModelColumn.java	Added documentation note about BanyanDB extension usage
changes.md	Added changelog entry for the fix
query-protocol.md	Updated trace query API documentation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}