fix(postcss): regression with user-defined rules not reloaded and kil…

…l astro plugin (#1956)

* fix(postcss): don't mess with initial css

let’s kill the @pandacss/astro plugin, it is the indirectly the root cause of many headaches

it forces us to track the initial CSS because of the base.css added on the fly

we reverted back to only caching it once because in astro (therefore in park-ui) we ended up with duplicated styles
but now for other postcss users (non-astro) we’re back to that issue of not tracking changes in the CSS that contains the @layer rules #1955

these changes work with vite, next and astro just fine, the only thing needed for astro users is to create a postcss file like this and import a css with the @layer rules (just like any other postcss users)

* chore(logs): better display for CssSyntaxError in sheet

* fix: ensure the outdir is always set

after a config change, the code path will go through DiffEngine.refresh + loadConfig instead of loadConfigAndCreateContext so the config.outdir might be empty if not provided in the panda.config

* BREAKING: remove @pandacss/astro in favor of just using @pandacss/postcss

* chore: add changesets

* chore: revert logs since a better one will land here #1957

.changeset/rich-phones-bake.md

@@ -0,0 +1,10 @@
+---
+'@pandacss/config': patch
+'@pandacss/node': patch
+---
+
+Fix an edge-case for when the `config.outdir` would not be set in the `panda.config`
+
+Internal details: The `outdir` would not have any value after a config change due to the fallback being set in the
+initial config resolving code path but not in context reloading code path, moving it inside the config loading function
+fixes this issue.

.changeset/thin-eyes-remain.md

@@ -0,0 +1,6 @@
+---
+'@pandacss/node': minor
+---
+
+Fix `@pandacss/postcss` plugin regression when the entry CSS file (with `@layer` rules order) contains user-defined
+rules, those user-defined rules would not be reloaded correctly after being changed.