Feature request: Multiple configuration flles

I am testing this extension for my work and we are working with a more complex setup of tailwind. We are experiencing some difficulties with the configuration field. So i hope this feature can be added to the extension or maybe someone else is having an idea for an easy way to have this complete configuration in the extension.

We have 2 presets which are extending on each other and 1 tailwind config for our site itself.

For example:
Site tailwind.config.js is including a customer wide preset and this preset is also an extension on our company wide preset.

**Tailwind.config.js** (we have multiple sites in only repository, every site is having an tailwind.config.js file extending on the customer preset used by all sites in the repository)
```
const customerBase = require('../customer_base/customer-base-preset');
/** @type {import('tailwindcss').Config} */
module.exports = {
presets: [customerBase],
content: [
....
```

**customer-base-preset.js**
```
const companyPreset = require('@CompanyNPMPackage/company_preset');
/** @type {import('tailwindcss').Config} */
module.exports = {
presets: [companyPreset],
content: [
....
```

**company_preset.js**
```
/** @type {import('tailwindcss').Config} */
module.exports = {
content: [
....
```

At this moment: We need to manually merge the files into one file so we can add it to the browser extension. When one of the files is updated, we need to merge the files again and debugging is hard when it is not working correct. We experienced some issues at our first run and had to remove some parts of the arrays which are working correct in our tailwind building.

Ideally we would like to use the identical configuration as we are using in our complete installation. As an alternative we would like to see support for adding multiple configurations to the extension to simulate the original setup of the installation.

I hope my issue clear and you understand the reason of my feature request. We really like this extension at the first runs but this issue is holding us back to use it company wide. Thank you in advance.

Start by comparing the extension's current configuration handling with the referenced tailwind.config.js, customer-base-preset.js, and company_preset.js files. Reproduce the manual merge scenario and determine how nested presets or multiple configurations should be represented; done means the extension can use the original setup without manual merging and preserves the working configuration arrays.

Escrito por el modelo de indexación a partir del texto del issue.