chore: format integration tests

[ghost]

Description

find . -type f -name Nargo.toml -exec sh -c 'cd "$(dirname "{}")" && nargo fmt &> /dev/null || echo "Failed in: $(dirname "{}")"' \;

Failed in: ./tooling/nargo_cli/tests/test_libraries/bad_name
Failed in: ./tooling/nargo_cli/tests/compile_failure/depend_on_bin
Failed in: ./tooling/nargo_cli/tests/compile_failure/package_name_empty
Failed in: ./tooling/nargo_cli/tests/compile_failure/custom_entry_not_found
Failed in: ./tooling/nargo_cli/tests/compile_failure/workspace_missing_toml
Failed in: ./tooling/nargo_cli/tests/compile_failure/workspace_missing_toml/crates/b
Failed in: ./tooling/nargo_cli/tests/compile_failure/invalid_dependency_name
Failed in: ./tooling/nargo_cli/tests/compile_failure/package_name_hyphen

Additional Context

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[ghost]

@jfecher

[jfecher]

Lets merge this now. There are some remaining parts that may be a bit questionable but overall I think there is a lot more that are good. For the remaining bits we can open issues for them and tackle them at a later date.

[TomAFrench]

I'm really not a fan of how the formatter is collapsing code sections separated with a blank line together if there's a comment between them. This severely hampers readability for me.

[ghost]

@TomAFrench, ok, I'll fix it