Do not panic when passed an invalid bootnode address

[tomaka]

Close #2204

We no longer panic when the chain spec contains an invalid bootnode address.

As I've commented in the code, it is not possible to be sure that a bootnode address is actually invalid. We can only be sure that smoldot cannot parse it, but that's not the same as saying that it's invalid.
For this reason, invalid bootnode addresses are simply ignored in the light client.

[mergify]

Automatically approving tomaka's pull requests. This auto-approval will be removed once more maintainers are active.

[github-actions]

twiggy diff report

Difference in .wasm size before and after this pull request.

---

 Delta Bytes │ Item
─────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       -2271 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h4db768a317f75bd7
       +2271 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::hf15ccf8a70d20b90
       +1391 ┊ alloc::str::join_generic_copy::h2b60db0ca0225613
        -964 ┊ <smoldot::chain_spec::FromGenesisStorageError as core::fmt::Display>::fmt::h3d8fdea000660d7c
        +964 ┊ <smoldot::chain_spec::FromGenesisStorageError as core::fmt::Display>::fmt::h88bbc34ef75f7114
        +711 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h1b4cd9f06cb36df2
        -711 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h733c3b8651cfb4ca
        +515 ┊ core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once::h4e9404b7c02c8ce1
        -417 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h0021740f386b88d3
        +417 ┊ <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h2621b010151d6ae0
        +404 ┊ smoldot_light_base::Client<TChain,TPlat>::add_chain::hf0c4531441a14584
        +392 ┊ core::ptr::drop_in_place<futures_util::future::future::remote_handle::Remote<core::future::from_generator::GenFuture<smoldot_light_base::Client<alloc::vec::Vec<futures_util::abortable::AbortHandle>,smoldot_light_wasm::platform::Platform>::add_chain<alloc::vec::into_iter::IntoIter<smoldot_light_base::ChainId>>::{{closure}}>>>::h3f9bf02353884686
        -392 ┊ core::ptr::drop_in_place<futures_util::future::future::remote_handle::Remote<core::future::from_generator::GenFuture<smoldot_light_base::Client<alloc::vec::Vec<futures_util::abortable::AbortHandle>,smoldot_light_wasm::platform::Platform>::add_chain<alloc::vec::into_iter::IntoIter<smoldot_light_base::ChainId>>::{{closure}}>>>::h4f3fe95ebde6ccd7
        +357 ┊ <futures_util::future::future::remote_handle::Remote<Fut> as core::future::future::Future>::poll::h2b96185b8a472863
        -357 ┊ <futures_util::future::future::remote_handle::Remote<Fut> as core::future::future::Future>::poll::h45ab72d6f0ea9c0d
        -302 ┊ <smoldot::libp2p::multiaddr::ParseError as core::fmt::Debug>::fmt::h29b691bf50afa559
        -259 ┊ <futures_util::future::future::catch_unwind::CatchUnwind<Fut> as core::future::future::Future>::poll::h8d914696536f9f3a
        +259 ┊ <futures_util::future::future::catch_unwind::CatchUnwind<Fut> as core::future::future::Future>::poll::hfac1c1a68fdf162e
        -143 ┊ futures_util::future::future::remote_handle::remote_handle::h020c0b31b1eeeaec
        +143 ┊ futures_util::future::future::remote_handle::remote_handle::h05a9bbed0b10ee10
        +854 ┊ ... and 49 more.
       +3961 ┊ Σ [69 Total Rows]

[melekes]

👍

[melekes]

do we really need continue here?