[UI v2] experiment: Adds basic spacing utilities as props and new layout components: Block and Flex

[devinvillarosa]

Laying out components with raw tailwwind is hard. There are too many options and tailwind classes to pass to simply lay components out. For example, when will I ever use mt-4.5?

This PR experiments in:

1. Creating a prop utilty and css classes using CVA to be able to pass layout properties as props. These props helps reduce the number of spacing options for the UI so that developers can think less and simplify spacing.

TLDR this PR limits these tailwind properties, provides them as props (which _can _ be added in our base components if needed), and adds <Block /> and <Flex /> components to make laying out components more declarative and reduce decision fatigue on what spacing levels to pass

2. Create a <Block /> and <Flex /> component that can be used to lay components out using the reduced options mentioned above.

Example

	return (
-		<div className="flex flex-row items-center gap-2">
+		<Flex flexDirection="row" gap={2} alignItems="center">
			<Typography variant="h4">Global Concurrency Limits</Typography>
			<Button onClick={onAdd} size="icon">
				<Icon id="Plus" />
			</Button>
-		</div>
+		</Flex>
	);

The example ☝️ creates a bit more declarative way of laying components out.

Another example

-		<div className="flex flex-row items-center gap-2">
+		<Flex flexDirection="row" gap={2} alignItems="center">
			<Typography variant="h4">Global Concurrency Limits</Typography>
			<Button onClick={onAdd} size="icon">
				<Icon id="Plus" />
			</Button>
-		</div>
+		</Flex>

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

Related to #15512

[devinvillarosa]

If we want to add these props to our components in the future, we can just do something like:

type Props = ButtonProps & UtilityProps
...
return <Button className={cn(buttonVariants({ variant, size, className }), spacingUtiltiesClasses(props))}  ... />

[desertaxle]

Similarly, we might want to omit display here so that this always stays flex.

[desertaxle]

Hooray for readability!