Refactor to use Engines where possible (FuelLabs#4225)

## Description

Small refactor to use `Engines` where possible, to promote code unity
across the codebase and reduce possibilities for code refactors in the
future.

## Checklist

~~- [ ] I have linked to any relevant issues.~~
~~- [ ] I have commented my code, particularly in hard-to-understand
areas.~~
~~- [ ] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).~~
~~- [ ] I have added tests that prove my fix is effective or that my
feature works.~~
- [x] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.

Co-authored-by: emilyaherbert <[email protected]>

sway-core/src/semantic_analysis/module.rs

@@ -29,8 +29,7 @@ impl ty::TyModule {
 
         // TODO: Ordering should be solved across all modules prior to the beginning of type-check.
         let ordered_nodes_res = node_dependencies::order_ast_nodes_by_dependency(
-            ctx.type_engine,
-            ctx.decl_engine,
+            ctx.engines(),
             tree.root_nodes.clone(),
         );