[Tracking] Consistent logging throughout `forc` with `tracing`

`forc`'s current approach to logging is quite inconsistent.

The aim is to use `tracing` throughout and take advantage of its support for customisable "subscriber"s to control things like filtering, whether to emit to `stdout`/`stderr`/file, and so on. While much of `forc`'s output already handles this correctly, much of it still writes directly to `stdout` or `stderr` - in particular, any formatted output and compiler output.

This is a tracking issue around making `forc`'s logging implementation more consistent.

## To-do

- [x] FuelLabs/forc#116.
- [x] FuelLabs/sway#1661.
- [x] FuelLabs/sway#2373.
- [ ] FuelLabs/forc#118.
- [x] FuelLabs/sway#1702.
- [x] FuelLabs/sway#2375.
- [x] FuelLabs/sway#2362.
- [ ] FuelLabs/sway#2364.
- [x] FuelLabs/sway#2305.

Start by reviewing the tracking issue and its checklist, especially the remaining forc#118 and sway#2364 items. Follow those referenced issues to identify the relevant logging and compiler-output work. The tracking goal is complete when the remaining unchecked items are addressed and forc consistently uses tracing instead of direct stdout or stderr writes.

Written by the indexing model from the issue text.