Related to #1547: use dioxus-cli within a workspace (wildcard-members, real package names)

[RGafiyatullin]

(Related to #1547)

Although the dx CLI allows to specify a package name to chose from workspace members, it does not support workspace members specified as glob-wildcards. Neither it respects the effective package name, specified in the crate's Cargo.toml.

This PR addresses that issue:

• upon dx build ..., if the --bin CLI-argument is provided, treat the current dir as a workspace;
• search through the workspace's members: resolve each of them with glob;
• assume that any workspace member has a Cargo.toml in it (cargo does it, so it's okay);
• read said manifest, and check the package name in it;
• if found — there we have our sought package.

[ealmloff]

It seems like this handles workspace names much better!

I'm curious what your use case is for glob patterns for the bin field?

I realize this PR doesn't introduce this error, but as a note, we don't actually need to assume that the current directory is the root of the package. We can use cargo-metadata to get the members of the workspace associated with the current path (even if we are in a different workspace member) https://docs.rs/cargo_metadata/latest/cargo_metadata/struct.Metadata.html#method.workspace_packages

[RGafiyatullin]

@ealmloff , I agree: invoking cargo-metadata should simplify the things.

I'm curious what your use case is for glob patterns for the bin field?

I do not use wildcards for the bin field, I use them to specify member-crates of a workspace.
E.g.

members = [
  "crates/lib/*",
  "crates/app/*"
]

[ealmloff]

Interesting, I didn't know that the workspace field had glob support!

[RGafiyatullin]

I had a look at how the rest of the CLI works: a lot of it could use moving to cargo-metadata...

[ealmloff]

This looks much better, thank you!