Fix annotations in file note functions

[newhoggy]

Changelog

- description: |
    Fix annotations in file note functions
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

The annotations were incorrect in the case of absolute file paths. Absolute file paths should not be prepended to.

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[carbolymer]

The check is redundant when using </>

Suggested change

	if isAbsolute filePath
	then H.annotate filePath
	else H.annotate $ cardanoCliPath </> filePath
	H.annotate $ cardanoCliPath </> filePath

[carbolymer]

Why are we annotating absolute paths, but returning a relative one only in this place? What issue does this function solve?

[carbolymer]

isAbsolute seems unnecessary