Rework 'Understanding the tables' (#629)

* Rework 'Understanding the tables'
* Relink destinations section
* Add staging and versioned datasets
* Rename the page and update the links
* Put destination tables after pipeline
* Update page content so it fits the new page name

docs/website/docs/build-a-pipeline-tutorial.md

@@ -391,7 +391,7 @@ utilization, schema enforcement and curation, and schema change alerts.
 which consist of a timestamp and pipeline name. Load IDs enable incremental transformations and data
 vaulting by tracking data loads and facilitating data lineage and traceability.
 
-Read more about [lineage.](dlt-ecosystem/visualizations/understanding-the-tables.md#load-ids)
+Read more about [lineage](general-usage/destination-tables.md#data-lineage).
 
 ### Schema Enforcement and Curation
 

docs/website/docs/dlt-ecosystem/destinations/filesystem.md

@@ -155,7 +155,7 @@ All the files are stored in a single folder with the name of the dataset that yo
 The name of each file contains essential metadata on the content:
 
 - **schema_name** and **table_name** identify the [schema](../../general-usage/schema.md) and table that define the file structure (column names, data types etc.)
-- **load_id** is the [id of the load package](https://dlthub.com/docs/dlt-ecosystem/visualizations/understanding-the-tables#load-ids) form which the file comes from.
+- **load_id** is the [id of the load package](../../general-usage/destination-tables.md#load-packages-and-load-ids) form which the file comes from.
 - **file_id** is there are many files with data for a single table, they are copied with different file id.
 - **ext** a format of the file ie. `jsonl` or `parquet`