To Reproduce Steps to reproduce the behavior:

1. Build qna.yaml
2. Do ilab taxonomy diff
3. Click on '....'
4. Scroll down to '....'
5. See error

Expected behavior

• ilab taxonomy diff should catch errors in the qna.yaml and notify users. However, the rules need to be in line with how users would build qna.yamls.

Screenshots

• Attached Image

Device Info (please complete the following information):

• Hardware Specs: [e.g. Apple M2 Pro Chip, 16 GB Memory, etc.]
• OS Version: [e.g. Mac OS 14.4.1, Fedora Linux 40]
• InstructLab Version: [output of \\\\\{{{}ilab --version{}}}]
• Provide the output of these two commands:
  • sudo bootc status --format json | jq .status.booted.image.image.image to print the name and tag of the bootc image, should look like registry.stage.redhat.io/rhelai1/bootc-intel-rhel9:1.3-1732894187
  • ilab system info to print detailed information about InstructLab version, OS, and hardware – including GPU / AI accelerator hardware

Bug impact

• The YAML linter used in 'ilab taxonomy diff' in the latest version is throwing an error when: 
  • There is no period added as a punctuation at the end of the line - it is catching this as a 'trailing space' in the qna.yaml.
  • It is limiting each line to 120 tokens. 

Known workaround

• Please add any known workarounds.

Additional context

• This was discovered in the POC workshop and a lot of the users ran into this issue, causing bad UX and time spent doing a lot of data engineering and cleanup. Greatly increases the time to value.