Prettier and Package Update

Azura Storage Blob and Trivago Prettier Sort Imports

Signed-off-by: Allan Carr <allan.carr@thinkimex.com>

_reference/reportFiltersAndSorters.md

@@ -3,7 +3,8 @@
 This documentation details the schema required for `.filters` files on the report server. It is used to dynamically
 modify the graphQL query and provide the user more power over their reports.
 
-# Special Notes
+## Special Notes
+
 - When passing the data to the template server, the property filters and sorters is added to the data object and will reflect the filters and sorters the user has selected
 
 ## High level Schema Overview
@@ -40,9 +41,10 @@ Filters effect the where clause of the graphQL query. They are used to filter th
 A note on special notation used in the `name` field.
 
 ## Reflection
+
 Filters can make use of reflection to pre-fill select boxes, the following is an example of that in the filters file.
 
-```
+```json
     {
       "name": "jobs.status",
       "translation": "jobs.fields.status",
@@ -67,7 +69,7 @@ The following cases are available
 - `special.employees` - This will reflect the employees `bodyshop.employees`
 - `special.first_names` - This will reflect the first names `bodyshop.employees`
 - `special.last_names` - This will reflect the last names `bodyshop.employees`
-- 
+
 ### Path without brackets, multi level
 
 `"name": "jobs.joblines.mod_lb_hrs",`
@@ -104,6 +106,7 @@ query gendoc_hours_sold_detail_open($starttz: timestamptz!, $endtz: timestamptz!
 ```
 
 ### Path with brackets,top level
+
 `"name": "[jobs].joblines.mod_lb_hrs",`
 This will produce a where clause at the `jobs` level of the graphQL query.
 
@@ -138,6 +141,7 @@ query gendoc_hours_sold_detail_open($starttz: timestamptz!, $endtz: timestamptz!
 ```
 
 ## Known Caveats
+
 - Will only support two level of nesting in the graphQL query `jobs.joblines.mod_lb_hrs` vs `[jobs].joblines.mod_lb_hrs` is fine, but `jobs.[joblines.].some_table.mod_lb_hrs` is not.
 - The `dates` object is not yet implemented and will be added in a future release.
 - The type object must be 'string' or 'number' and is case-sensitive.
@@ -146,10 +150,12 @@ query gendoc_hours_sold_detail_open($starttz: timestamptz!, $endtz: timestamptz!
 - Do not add the ability to filter on things like FK constraints, must like the above example.
 
 ## Sorters
+
 - Sorters follow the same schema as filters, however, they do not do square bracket wrapping to indicate level hoisting, a filter added on `job.md_status` would be added at the top level, and a filter added on `jobs.joblines.mod_lb_hrs` would be added at the `joblines` level.
 - Most of the reports currently do sorting on a template level, this will need to change to actually see the results using the sorters.
 
 ### Default Sorters
+
 - A sorter can be given a default object containing a `order` and `direction` key value. This will be used to sort the report if the user does not select any of the sorters themselves.
 - The `order` key is the order in which the sorters are applied, and the `direction` key is the direction of the sort, either `asc` or `desc`.
 
@@ -164,4 +170,4 @@ query gendoc_hours_sold_detail_open($starttz: timestamptz!, $endtz: timestamptz!
         "direction": "asc"
     }
 }
-```
+```