error: merge crate nydus-error into nydus-utils and nydus-api

[jiangliu]

Merge crate nydus-error into nydus-utils and nydus-api, to reduce number of crates.

Types of changes

What types of changes does your PullRequest introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

Go over all the following points, and put an x in all the boxes that apply.

• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[anolis-bot]

@jiangliu , a new test job has been submitted. Please wait in patience. The test job url: https://tone.openanolis.cn/ws/nrh4nnio/test_result/74723

[codecov]

Codecov Report

Merging #1299 (016b260) into master (809f8d9) will decrease coverage by 0.16%.
The diff coverage is 2.73%.

@@            Coverage Diff             @@
##           master    #1299      +/-   ##
==========================================
- Coverage   46.06%   45.90%   -0.16%     
==========================================
  Files         124      123       -1     
  Lines       36934    37009      +75     
  Branches    36934    37009      +75     
==========================================
- Hits        17012    16990      -22     
- Misses      19033    19124      +91     
- Partials      889      895       +6     

Impacted Files	Coverage Δ
api/src/error.rs	60.71% <0.00%> (ø)
api/src/http.rs	0.00% <0.00%> (ø)
api/src/http_handler.rs	55.12% <ø> (ø)
api/src/lib.rs	50.00% <ø> (ø)
rafs/src/lib.rs	61.98% <ø> (ø)
service/src/lib.rs	75.64% <ø> (ø)
src/bin/nydusd/main.rs	0.19% <ø> (ø)
src/lib.rs	52.50% <ø> (ø)
storage/src/lib.rs	28.57% <ø> (ø)
utils/src/lib.rs	82.89% <ø> (ø)
... and 3 more

... and 4 files with indirect coverage changes

[anolis-bot]

@jiangliu , the code has been updated, so a new test job has been submitted. Please wait in patience. The test job url: https://tone.openanolis.cn/ws/nrh4nnio/test_result/74724

[anolis-bot]

@jiangliu , The CI test is completed, please check result:

Test Case		Test Result
build rust golang image		✅ SUCCESS
compile nydusd		❌ FAIL

Sorry, your test job failed. Please get the details in the link.

[anolis-bot]

@jiangliu , The CI test is completed, please check result:

Test Case		Test Result
build rust golang image		✅ SUCCESS
compile nydusd		✅ SUCCESS
compile ctr remote		✅ SUCCESS
compile nydus snapshotter		✅ SUCCESS
run container with rafs		✅ SUCCESS
run container with zran		✅ SUCCESS
run container with rafs and compile linux		✅ SUCCESS

Congratulations, your test job passed!

[liubogithub]

eother macro is in the same crate, why do we need to replace eother!?

[jiangliu]

It's a limitation of rust,

error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
  --> api/src/config.rs:17:5
   |
17 | use crate::eother;
   |     ^^^^^^^^^^^^^
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>
note: the macro is defined here
  --> api/src/error.rs:33:9
   |
33 | /         macro_rules! $fn {
34 | |             () => {
35 | |                 std::io::Error::new($err.kind(), format!("{}: {}:{}", $err, file!(), line!()))
36 | |             };
...  |
39 | |             };
40 | |         }
   | |_________^
...
82 |   define_error_macro!(eother, std::io::Error::new(std::io::ErrorKind::Other, ""));
   |   ------------------------------------------------------------------------------- in this macro invocation
   = note: `#[deny(macro_expanded_macro_exports_accessed_by_absolute_paths)]` on by default
   = note: this error originates in the macro `define_error_macro` (in Nightly builds, run with -Z macro-backtrace for more info)

error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
    --> api/src/config.rs:1258:17
     |
1258 |                 crate::eother!("test");
     |                 ^^^^^^^^^^^^^
     |
     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
     = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>
note: the macro is defined here
    --> api/src/error.rs:33:9
     |
33   | /         macro_rules! $fn {
34   | |             () => {
35   | |                 std::io::Error::new($err.kind(), format!("{}: {}:{}", $err, file!(), line!()))
36   | |             };
...    |
39   | |             };
40   | |         }
     | |_________^
...
82   |   define_error_macro!(eother, std::io::Error::new(std::io::ErrorKind::Other, ""));
     |   ------------------------------------------------------------------------------- in this macro invocation
     = note: this error originates in the macro `define_error_macro` (in Nightly builds, run with -Z macro-backtrace for more info)

[liubogithub]

OK, I get it.