Support for Ordered Groups Without Redundant Configuration

[BijanProgrammer]

Description:
Currently, to enforce a specific order for import groups (e.g., @/assets before @/components), we must explicitly list each group in importOrder, leading to redundant configuration. I’d like to request a feature that allows specifying the order without listing each group separately.

Current Behavior:
To achieve the following order with separators:

1. react imports
2. next/* imports
3. @/assets
4. @/components
5. @/dto
6. @/icons
7. @/utils
8. CSS imports

I have to configure it like this:

{
  "plugins": ["@trivago/prettier-plugin-sort-imports"],
  "importOrder": [
    "^react$",
    "^next",
    "^@/assets",
    "^@/components",
    "^@/dto",
    "^@/icons",
    "^@/utils",
    ".*\\.(css)$"
  ],
  "importOrderSeparation": true,
  "importOrderSortSpecifiers": true
}

However, the group definitions (@/assets, @/components, etc.) are redundant.

Requested Feature:
It would be great to add a flag or configuration option that automatically groups imports based on their parent directory structure. For example, imports from @/assets would automatically be grouped separately from those in @/components without needing to explicitly list each folder in importOrder. This flag would ensure that imports from different parent folders are placed in different groups with separators, without the need to manually define every group.

Example:

{
  "importOrder": [
    "^react$",
    "^next",
    "^@/",
    ".*\\.(css)$"
  ],
  "importOrderSeparation": true,
  "autoGroupByParentDirectory": true
}

With the autoGroupByParentDirectory flag enabled, imports from different directories under @/ (like @/assets, @/components, @/utils, etc.) would automatically be separated into distinct groups with appropriate newlines between them.

Why This Matters:

• Reduces boilerplate in .prettierrc
• Easier to maintain as new groups are added
• Keeps import sorting simple while still allowing structured organization

Would love to hear thoughts on whether this could be supported or if there's an alternative approach I might have missed. Thanks for the great work on this plugin! 🚀