[docs] Replace "Compaction Service" to "Tiering Service" in all images (#576)

* [docs] Update "Compaction Service" to "Tiering Service" in images

* fix

Author: wuchong

…s/install-deploy/deployment_overview.png …site/docs/assets/deployment_overview.pngwebsite/docs/install-deploy/deployment_overview.png renamed to website/docs/assets/deployment_overview.png website/docs/install-deploy/deployment_overview.png renamed to website/docs/assets/deployment_overview.png

@@ -10,7 +10,7 @@ Below, we provide an overview of the key components of a Fluss cluster, detailin
 
 The figure below shows the building blocks of Fluss clusters:
 
-<img width="1200px" src={require('./deployment_overview.png').default} />
+<img width="1200px" src={require('../assets/deployment_overview.png').default} />
 
 
 

website/docs/assets/streamhouse.png

@@ -16,4 +16,4 @@ in the well-known open data lake format for better analytics performance. Curren
 
 The overall tiered storage architecture is shown in the following diagram:
 
-<img width="600px" src={require('./tiered-storage.png').default} />
+<img width="600px" src={require('../../assets/tiered-storage.png').default} />

…enance/tiered-storage/tiered-storage.png website/docs/assets/tiered-storage.pngwebsite/docs/maintenance/tiered-storage/tiered-storage.png renamed to website/docs/assets/tiered-storage.png website/docs/maintenance/tiered-storage/tiered-storage.png renamed to website/docs/assets/tiered-storage.png

@@ -28,11 +28,11 @@ Fluss is a streaming storage supporting streaming reads and writes with sub-seco
 With [Lakehouse Storage](maintenance/tiered-storage/lakehouse-storage.md), Fluss unifies data streaming and data Lakehouse by serving real-time streaming data on top of Lakehouse.
 This not only brings low latency to data Lakehouse, but also adds powerful analytics to data streams.
 
-In order to build Streaming Lakehouse, Fluss maintains a compaction service to compact the real-time data in Fluss cluster into Lakehouse storage.
+To build a Streaming Lakehouse, Fluss maintains a tiering service that compacts real-time data from the Fluss cluster into the data lake format stored in the Lakehouse Storage.
 The data in Fluss cluster (streaming Arrow format) is write-optimized for low-latency read and write, and the compacted data in Lakehouse (Parquet format with compressions) is read-optimized for powerful analytics and space-optimized for storing long-term data.
 So the data in Fluss cluster serves real-time data layer which retains days with sub-second-level freshness, and the data in Lakehouse serves historical data layer which retains months with minute-level freshness.
 
-![streamhouse](streamhouse.png)
+![streamhouse](../assets/streamhouse.png)
 
 The core idea of Streaming Lakehouse is shared data and shared metadata between stream and Lakehouse, avoiding data duplication and metadata inconsistency.
 Some powerful features it provided are: