Fixed word boundary tests on paths

[cognitivegears]

Please check if the PR fulfills these requirements

• [ X ] The commit message follows our guidelines
• [ X ] Tests for the changes have been added (for bug fixes / features)
• [ N/A ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)
Currently, the boundary option is not respected when testing file paths. This is due to a difference between the matching code used for testing normal text and paths.

What is the new behavior (if this is a feature change)?
Changed the functionality to respect word boundaries, matching the functionality of line tests.

Does this PR introduce a breaking change? (What changes might users need to make due to this PR?)
Only if a consumer of the tool expects files name matching and content matching to differ for word boundaries, probably unlikely.

Other information:
N/A

Fixes #94

[codecov]

Codecov Report

Merging #93 (7c794de) into main (f86ffb4) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage   95.60%   95.60%           
=======================================
  Files          21       21           
  Lines         478      478           
=======================================
  Hits          457      457           
  Misses         12       12           
  Partials        9        9           

Impacted Files	Coverage Δ
pkg/result/pathresult.go	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f86ffb4...7c794de. Read the comment docs.