feat: tailwind configuration works in mono repos

[mnahkies]

Description

Previously the tailwind configuration only worked if the directory structure looked like:

/root
├── package.json
├── pages
├── evidence.plugins.yaml
├── ...
├── .evidence
│   └── template
│       ├── tailwind.config.cjs
│       └── node_modules # ./node_modules
│           └── some-module
│               └── dist/**/*.{html,js,svelte,ts,md}  
└── node_modules # ../../node_modules
    └── some-module
        └── dist/**/*.{html,js,svelte,ts,md}  

This PR aims to replace the assumptions on possible node_modules locations with following the same package resolution algorithm used elsewhere in the sdk, meaning that a hoisted monorepo layout like this will now work:

/root
├── package.json
├── node_modules
│   └── some-module # will now work
│       └── dist/**/*.{html,js,svelte,ts,md}  
└── packages
    └── my-evidence-proj
        ├── package.json
        ├── node_modules
        │   └── some-other-module # will still work
        │       └── dist/**/*.{html,js,svelte,ts,md}
        ├── pages
        ├── evidence.plugins.yaml
        ├── ...
        └── .evidence
            ├── template
            └── tailwind.config.cjs

There remains an assumption/convention that packages must structure their artifacts into a /dist/**/*.{html,js,svelte,ts,md} path, but that seems fine to leave alone.

Checklist

• For UI or styling changes, I have added a screenshot or gif showing before & after
• I have added a changeset
• I have added to the docs where applicable
• I have added to the VS Code extension where applicable

[mnahkies]

Using sync filesystem access, as calling from a synchronous context in the tailwind config

[mnahkies]

Using a dedicated export, as needs to be required from a commonjs context, and esm only modules are included in the main ./plugins export

[ItsMeBrianD]

A few notes on this one;

1. I think we can rather easily convert tailwind configuration from .cjs to .mjs, should help us avoid needing to add another export path to the sdk (we have our ideal end state for the package documented in the monorepo roadmap doc
2. This is not working for me when I run it locally in our monorepo, but the next branch does still work - there might be a regression here