More advanced `group_imports` with 4 groups and adaptable "std-like" crates

In code i write i have taken to group the import statements into 4 groups:

1. "std-like" crates which include all the normal std crates (std, alloc, core) and large crates like tokio or frameworks like axum or bevy pretty much everything which fundamentaly controls how my code will look like.
2. Other external crates
3. Workspace internal crates
4. Crate internal imports

I have thought about trying to implement this in rustfmt, but i don't know how doable this is.
I guess making crates in 1. optionally configurable shouldn't be that hard, but does rustfmt get any workspace information? Is it feasible to optionally implement retrieving workspace information for such a feature, or would this require some larger architectural/conceptual change?

Thanks in advance :)

Start by examining rustfmt's existing import-grouping configuration and determine whether it has access to workspace information. Then assess how configurable "std-like" crates and four import groups would fit the formatter's architecture. Done means establishing whether the feature is feasible and defining its required configuration and workspace behavior.