Too restrictive check in Task insertion

[samuelbray32]

• #1278 made a check for equivalency of secondary keys when ingesting a Task that already existed in the Task table code
• Since the task description is not an enumerated value, this can cause failure where probably unecessary:
  • Example error: Task Sleep already exists with different values for task_description: sleeping != The animal sleeps in a small empty box

Proposal On mismatch, ask user whether to accept linking to the existing value rather than immediately erroring

[CBroz1]

Makes sense

Eric and I were chatting recently related to #1299 about ways to user-prompt close-enough matches