refactor(core): Add ErrorKind InvalidInput to indicate users input error

[dqhl76]

If user try to seek for a invalid position, we will give an Unexpected Error. Unexpected Error used to represent OpenDAL don't know what happened here. I think it may be better to use a new error kind InvalidInput to represent this situation.

    /// OpenDAL don't know what happened here, and no actions other than just
    /// returning it back. For example, s3 returns an internal service error.
    Unexpected,

before:

  2023-07-14T06:37:19.152933Z ERROR opendal::services: service=memory operation=Reader::seek path=bfae56eb-ae99-4ca6-b000-4bdad69c85e1 read=0 -> data read failed: Unexpected (permanent) at Reader::seek => invalid seek to a negative or overflowing position

Context:
    service: memory
    path: bfae56eb-ae99-4ca6-b000-4bdad69c85e1

    at core/src/layers/logging.rs:1108

after:

  2023-07-14T07:50:38.166551Z ERROR opendal::services: service=memory operation=Reader::seek path=0fca6ade-8d96-44fc-ac5b-86a370b26048 read=0 -> data read failed: InvalidInput (permanent) at Reader::seek => invalid seek to a negative or overflowing position

Context:
    service: memory
    path: 0fca6ade-8d96-44fc-ac5b-86a370b26048

    at core/src/layers/logging.rs:1108
    

related:#2636 (comment)
fix: #2636

[Xuanwo]

Thanks!

[Xuanwo]

Would you like to submit a new PR to add the test case in our behavior test?

[dqhl76]

Would you like to submit a new PR to add the test case in our behavior test?

Sure!