Method `as_slice` may be added to the standard library

[fabaff]

Is your feature request related to a problem? Please describe.

Get rid of the warning that tell the method with that name may be added to the standard library in the future.

....
   Compiling bincode v2.0.1
   Compiling libafl_targets v0.15.4 (/build/source/crates/libafl_targets)
error: a method with this name may be added to the standard library in the future
   --> crates/libafl/src/executors/forkserver.rs:831:40
    |
831 |                 .copy_from_slice(input.as_slice());
    |                                        ^^^^^^^^
    |
    = warning: once this associated item is added to the standard library, the ambiguity may cause an error or change in behavior!
    = note: for more information, see issue #48919 <https://github.com/rust-lang/rust/issues/48919>
    = help: call with fully qualified syntax `libafl_bolts::AsSlice::as_slice(...)` to keep using the current method
    = note: `-D unstable-name-collisions` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(unstable_name_collisions)]`

Describe the solution you'd like

Fixing the source instead of using the alternative 😉

Describe alternatives you've considered

Using -A unstable-name-collisions to suppress the warning.

[domenukk]

That's super annoying lol, there is no better name for this

[domenukk]

Any ideas?

[mannubaveja007]

Hi!

One option that came to me by researching is .copy_from_slice(AsSlice::as_slice(&input));

It's not the prettiest by the way, but it avoids the renaming of trait method.
second one is renaming one which can break the things

Happy to open a PR for whichever approach you prefer!