refactor(connector): avoid anyhow in `AccessError` and avoid using `RwError` if possible #14874

3 / 4 tasks completed

1 task still to be completed

Task	Status
Avoid `anyhow` in `AccessError`, as it's used in parsing and capturing backtraces per record is not acceptable in performance. This PR uses a plain `String` instead and provide similar experience to `anyhow` for constructing leaf errors by `thiserror_ext::Macro`.	Incomplete
Use `AccessError` as much as possible for parsing-related code logic, instead of using `RwError`.	Incomplete
I have written necessary rustdoc comments	Completed
I have added necessary unit tests and integration tests	Completed
All checks passed in `./risedev check` (or alias, `./risedev c`)	Completed
My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)	Incomplete