[Bug]: All TaskNotes Views include subtasks that don't match the "Task Identification" settings

[renatomen]

Bug Description

Given TaskNotes Plugin setting maps "Project" to a property named "Parent"
AND a Tasknotes "Task Identificatioin" -> Task Tag is set to "t/ef"

WHEN I create a note titled "Random_Note"
AND the Random_Note DOES NOT contain any tags
AND the Random_Note's "Parent" property value includes a link to a an existing "TaskNotes Task" titled "Existing_Task"
THEN 👇

Unexpected Behaviour

⛔The Random_Note is displayed as a subtask of "Existing_Task"

Expected Behaviour

👍The Random_Note IS NEVER displayed as a TaskNote result as a Task, nor Subtask

Reason for the expected behaviour

Makes Task Identification inconsistet. Violates the "Task tag" setting which determines "how Tasknotes identifies notes as tasks"

Demo Video

Impact on workflow

In vaults where projects and tasks can be a "Parent" of tasks and non-task notes, the non-task notes pollute the TaskNotes resutls. This is even worse for large projects with lots of documents.

In my workflow, the "Parent - Child" relationship is determined by the "in" property.
E.g:
🚧Project A
|_ ☑️Task A1
|_ ☑️Task A2
|_ ☑️Task A3
|_ 📝Note NA1
|_ 📝Note NA2
|_ 📝Note NA3

When managing tasks, I only want to see Task A1, Task A2, Task A3 under Project A.

For users with workflows in where seeing documents as subtasks is desirable, they can always add a tag to the document to make it "visible" in their TaskNotes results.

The current behaviour offers no easy way to exclude no-task notes from subtasks results.