fix!: introduce a new btime term to align ctime with Unix

[sxyazi]

Fixes #1760

This is a tricky issue. The initial introduction of ctime was just to correspond with the "created time" in Rust:

yazi/yazi-shared/src/fs/cha.rs

Line 46 in 558d97d

ctime: m.created().ok(),

which isn't a problem on non-Unix platforms.

However, in Unix, ctime has a different meaning — it refers to "changed time" which indicates when file attributes changed, yet it's distinct from mtime ("modified time") which indicates when file content is modified.

This PR attempts to address the issue fundamentally by aligning with Unix. This way, Yazi behaves correctly on Unix platforms, while also being fine on non-Unix platforms since they don't have the concept of ctime at all, and then we'll always use btime to represent a file's "created time", i.e. "birth time".

⚠️ Breaking changes

Renamed created to btime, modified to mtime for the sort_by option

# yazi.toml
[manager]
- sort_by = "created"
+ sort_by = "btime"

- sort_by = "modified"
+ sort_by = "mtime"

Renamed ctime to btime for the linemode command

# keymap.toml
- { on = [ "m", "c" ], run = "linemode ctime"  }
+ { on = [ "m", "b" ], run = "linemode btime" }

Renamed created to btime, modified to mtime for the sort command

# keymap.toml
- { on = [ ",", "c" ], run = "sort created" }
+ { on = [ ",", "b" ], run = "sort btime" },

# keymap.toml
- { on = [ ",", "m" ], run = "sort modified" }
+ { on = [ ",", "m" ], run = "sort mtime" }

Renamed the created, modified, accessed, length, and permissions properties of the Cha

• created => btime
• modified => mtime
• accessed => atime
• length => len
• permissions => perm

Note that the old names are still available, but a deprecation warning will shown — they will be completely removed in the next major version 0.4.2.