feat: Use indentation to separate global & code block query explanation

[claremacrae]

Description

Use indentation in the explain output, so that it is easier to see which instructions are from the Global Query, and which from the Tasks Query Block.

Motivation and Context

I've been finding that it's quite hard to see the end of the Global Query explanation and the start of the Tasks Query Block explanation in my main vault.

How has this been tested?

• Updating and adding automated tests
• Exploratory testing in the demo vault.

Screenshots (if appropriate)

Before:

Explanation of the global query:

heading includes tasks

No grouping instructions supplied.

At most 50 tasks.

Explanation of this Tasks code block query:

not done

due next week =>
  due date is between:
    2022-10-24 (Monday 24th October 2022) and
    2022-10-30 (Sunday 30th October 2022) inclusive

No grouping instructions supplied.

After

Explanation of the global query:

  heading includes tasks

  No grouping instructions supplied.

  At most 50 tasks.

Explanation of this Tasks code block query:

  not done

  due next week =>
    due date is between:
      2022-10-24 (Monday 24th October 2022) and
      2022-10-30 (Sunday 30th October 2022) inclusive

  No grouping instructions supplied.

Types of changes

Changes visible to users:

• New feature (prefix: feat - non-breaking change which adds functionality)
• Documentation (prefix: docs - improvements to any documentation content for users)

Internal changes:

• Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
• Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Checklist

• My code follows the code style of this project and passes yarn run lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change has adequate Unit Test coverage.

Terms

• My contribution follow this project's contributing guide
• I agree to follow this project's Code of Conduct