docs: enhance how references are generated (#5805)

* adjusted configurations

* enhancements to tool and configurations

* change reference in docs

* fixed issue in workflows reference

* added project name

* more optimizations

* fix context error

* added a types reference

* resolved missing types

* fix reference reflection types not having children

* add an expand url parameter

* added new option to the README

* added details about new option

www/apps/docs/content/modules/price-lists/backend/override-price-selection-strategy.mdx

@@ -262,7 +262,7 @@ You can learn more about optional properties and the meaning behind every proper
           },
           {
             name: "prices",
-            type: "[MoneyAmount](../../../references/entities/classes/MoneyAmount.mdx)[]",
+            type: "[MoneyAmount](../../../references/entities/classes/entities.MoneyAmount.mdx)[]",
             description: "The prices of the variant retrieved using the `context` object. It can include its original price and its price lists if there are any.",
             optional: false
           }

www/apps/docs/content/modules/price-lists/price-lists.md

@@ -20,7 +20,7 @@ Price lists can be used for a variety of use cases including:
 
 ### Price List Entity Overview
 
-A price list is stored in the database as a [PriceList](../../references/entities/classes/PriceList.mdx) entity. Some of its important attributes are:
+A price list is stored in the database as a [PriceList](../../references/entities/classes/entities.PriceList.mdx) entity. Some of its important attributes are:
 
 - `type`: The price list's type. Can be either a `sale` or an `override`.
 - `status`: The status of the price list. Can be `active` or `draft`. If a price list is a `draft`, its prices won't be applied even if its conditions are met.