Add `no_std` support for `dasp_graph`, enabling `all-no-std` feature to include `dasp_graph`.

[PanieriLorenzo]

There are several TODOs about this, referencing the fact that we can't make a global no_std feature because dasp_graph is not no_std. This is because petgraph did not use to have no_std support, but it does now: petgraph/petgraph#747 since version 0.8.0.

There's no reason not to close these TODOs now, other than maybe wanting to keep petgraph to an older version to avoid breakage?

For context, the TODOs in question are the following:

• dasp/dasp/src/lib.rs

  Line 109 in d089297

  // TODO: Remove `std` requirement once `dasp_graph` gains `no_std` support.

• dasp/dasp/Cargo.toml

  Line 31 in d089297

  # TODO: Move these into `all-no-std` once `dasp_graph` gains `no_std` support.

• dasp/dasp_graph/src/lib.rs

  Line 123 in d089297

  //! *TODO: Adding support for `no_std` is pending the addition of support for `no_std` in petgraph.