[Bug]: NLP Erroneous Autofill for "high" and "low" (and possibly others)

[RumiaKitinari]

Bug Description

Upon 1.) editing the value fields for priority (e.g., high -> 5-high, low -> 2-low), and 2.) using NLP shortcuts to select a priority, residual elements are left.

For example, for a NLP input test !2-low, the priority is registered as 2-low but also the task is called test !2- (with the residual element !2-).

Most likely, this is because low and high are associated with underlying keywords (e.g., I can just type low and 2-low will be the priority), and said keywords are being prioritized over the full priority string, thereby leaving the residual.

NOTE: This, interestingly, does not occur for normal (or 3-norm, as it is in my notes). I only observed the behavior for low / high.

Steps to Reproduce

1. Modify the value field of default priorities to (e.g., 5-high and 2-low).
2. Create a task using NLP, and use ! (the default shortcut for priority) and type whatever characters to select high / low (I just type "hi" and press ENTER).
3. Issue should occur.

TaskNotes Debug Info

Affected Task Frontmatter

Relevant Bases File Content

Relevant Settings or Customizations

No response

Console Errors or Logs

Screenshots or Screen Recording