v2.6.1 broke compatiblity

[KOBA789]

v2.6.1 renamed "entries" field in Telemetry.
This change should bump up major version.

error[E0609]: no field `entries` on type `&Telemetry`
   --> src/access/tlm/schema.rs:107:54
    |
107 |         let fields = Box::new(iter_fields(&telemetry.entries).filter_map(|(obs, field)| {
    |                                                      ^^^^^^^ unknown field
    |
    = note: available fields are: `name`, `metadata`, `content`

For more information about this error, try `rustc --explain E0609`.
error: could not compile `gaia-ccsds-c2a` (lib) due to 1 previous error
error: failed to verify package tarball
Error: Process completed with exit code 101.

https://github.com/arkedge/gaia/actions/runs/12824541755/job/35760854684

[sksat]

I strongly agree > This change should bump up major version

BUT on the other hand, we have already had some discussions and internal announcements regarding "v3" (ex: #26 ), so we can't bump up major naively............

[sksat]

We have multiple "compatibility" aspects of "tlmcmddb".
As a result, compatibility handling (& actual versioning) must take all of these into consideration.

• TlmCmdDB CSV format
• TlmCmdDB directory path
  • this is actually standardized in c2a-core
• TlmCmdDB editor experience (*.xlsm)
• crate Library API (this issue problem)
• tlmcmddb.json format (tlmcmddb.json の互換性が一部失われてしまっている #98 problem)

In addition, since "tlmcmddb" is a schema arrangement, the most careful attention of these needs to be given to data compatibility (not code).

[sksat]

Also, this is not a 2.6.1 issue, but a 2.6 issue; the changes included in 2.6 were previously found to have broken other compatibilities, and 2.6.0 is yanked.

Therefore, the option exists to yank it again and release 2.6.2, although (library) compatibility cannot be ensured unless we give up #24 entirely, since it is caused by an intentional change in the public field.