Fix warning by dev/release profiles from member Cargo.toml to workspace Cargo.toml.

[luqmana]

Clear up the warning about "profiles for the non root package will be ignored" by moving these to the workspace root.

If we need to, we can add specific workspace member overrides though that does come with the limitation that you can't specify panic, lto or rpath settings. Another limitation is if we publish one of the binary workspace members then cargo install does would not use the workspace root profile settings (details).

[smklein]

Clear up the warning about "profiles for the non root package will be ignored" by moving these to the workspace root.

If we need to, we can add specific workspace member overrides though that does come with the limitation that you can't specify panic, lto or rpath settings. Another limitation is if we publish one of the binary workspace members then cargo install does would not use the workspace root profile settings (details).

This might be a bit overkill, what happens if we define these profiles in the workspace and the non-root packages? Would that resolve the cargo install case?

[luqmana]

Clear up the warning about "profiles for the non root package will be ignored" by moving these to the workspace root.
If we need to, we can add specific workspace member overrides though that does come with the limitation that you can't specify panic, lto or rpath settings. Another limitation is if we publish one of the binary workspace members then cargo install does would not use the workspace root profile settings (details).

This might be a bit overkill, what happens if we define these profiles in the workspace and the non-root packages? Would that resolve the cargo install case?

In that case you'll get the same warning again about the profile settings being ignored for those non-root packages.