tracking issue for known issues with the analyzer switch to --use-fasta-parser

[devoncarew]

This collects the known failures from the switchover (without any particular prioritization):

• analyzer test failures when switching the parser to fasta analyzer test failures when switching the parser to fasta #33992
• analyzer language2 test failures when switching the parser to fasta Constant evaluation error in vm/reflect_core_vm_test when switching the parser to fasta #33994
  The above issue appears to be a const evaluation issue
• analyzer co19_2 test failures when switching the parser to fasta analyzer co19_2 test failures when switching the parser to fasta #33995
  • fixed the parser related issues and many (all?) of the remaining are pre-existing issues
• DDC test failures related to moving the analyzer to --use-fasta-parser two DDC test failures related to moving the analyzer to --use-fasta-parser #34041
  • expected to be resolved by the move to DDK
• support generalized void Analyzer: Support generalized void #30177

cc @danrubel @bwilkerson @kmillikin