Sort upgraded CSS

[RobinMalfait]

During the migration process, a lot of changes to the CSS file happen. Some parts are converted, some parts are deleted and some new CSS is added.

To make sure we are generating a sensible and good looking CSS file, we will sort the final CSS and pretty print it.

The order we came up with looks like this:

/* Imports */
@import "tailwindcss";
@import "../other.css";

/* Configuration */
@config "../path/to/tailwindcss.config.js";

@plugin "my-plugin-1";
@plugin "my-plugin-2";

@source "./foo/**/*.ts";
@source "./bar/**/*.ts";

@variant foo {}
@variant bar {}

@theme {}

/* Border compatibility CSS */
@layer base {}

/* Utilities */
@utility foo {}
@utility bar {}

/* Rest of your own CSS if any */

[philipp-spiess]

Let's gooo it's so good to read the diff of the integration test snapshots haha. Some comments inline, mostly not sure about the change log thing 🤔

[philipp-spiess]

The current message makes it sound like the order was wrong or something but the change is only really for esthetic reasons, what do you think about this? I tried to not use the word order since it has an inherent meaning in CSS and am trying to lean on the "restructure" terminology

Suggested change

	- _Upgrade (experimental)_: Sort upgraded CSS ([#14866](https://github.com/tailwindlabs/tailwindcss/pull/14866))
	- _Upgrade (experimental)_: Restructure the generated CSS to make it easier to read ([#14866](https://github.com/tailwindlabs/tailwindcss/pull/14866))

Also this doesn't really fix anything so maybe it shouldn't be in the fixed category either I think 🤔

I am still not convinced this is a very good message, maybe maybe this just doesn't need a changelog entry at all haha

[RobinMalfait]

Yeah hmm, maybe this is just an internal refactor. Especially because the codemods are not idempotent right now meaning you only will be able to run them once anyway. So it's still a single 'upgrade' and not a fix to previous upgrades from the user's perspective.