Update ZORDER blog with Liquid Clustering info (#493)

* Update ZORDER blog with Liquid Clustering info

Signed-off-by: Nick Karpov <nick@nickkarpov.com>

* fixed signoff error & linting

Signed-off-by: Nick Karpov <nick@nickkarpov.com>

---------

Signed-off-by: Nick Karpov <nick@nickkarpov.com>

src/blog/2023-06-03-delta-lake-z-order/index.mdx

@@ -8,6 +8,16 @@ date: 2023-06-03
 
 This blog post explains how to Z ORDER Delta tables and how this design pattern can significantly speed up your queries.
 
+<Info level="warning">
+  A new feature for simplifying data layout to optimize query performance has
+  been introduced since this blog was written. While this blog is still current,
+  and Z-ORDER continues to be supported, **Liquid Clustering** provides
+  flexibility to redefine clustering columns without rewriting existing data,
+  allowing data layout to evolve alongside analytic needs over time. You can
+  learn more about it in the [Delta Lake
+  documentation](https://docs.delta.io/latest/delta-clustering.html).
+</Info>
+
 Z Ordering your data reorganizes the data in storage and allows certain queries to read less data, so they run faster. When your data is appropriately ordered, more files can be skipped.
 
 Z Order is particularly important for the ordering of multiple columns. If you only need to order by a single column, then simple sorting suffices. If there are multiple columns, but we always/only query a common prefix of those columns, then hierarchical sorting suffices. Z Ordering is good when querying on one or multiple columns. You’ll see a concrete example later to further illustrate when Z Ordering fits well.