Comment tricks vsg into incorrect parsing state

Environment Ubuntu 20.04 VSG 3.23.0

Describe the bug Certain comments can cause the vsg parser to think it is parsing statements that it isn't.

In the example below, vsg thinks it is interpreting a procedure call statement, when it is actually an if else.

To Reproduce Run vsg against a file with this content:

-- [*a*/D]
library ieee;
use ieee.std_logic_1164.all;

entity uut is
    port (
        a : in  boolean;
        b : out std_logic
    );
end entity;

architecture rtl of uut is
begin

    process
    begin
        if a then
            b <= '0';
        else
            b <= '1';
        end if;
    end process;

end architecture;

FYI: This is a drastically cut down and modified version of a file generated by Xilinx Vivado. The comment that has been reduced to [*a*/D], is actually an XDC set_false_path constraint that looks up a pin using the * glob.

Expected behavior vsg should complete parsing this file.

Screenshots When the above is run through vsg:

> vsg error.vhd

Error: Unexpected token detected while parsing procedure_call_statement @ Line 19, Column 9 in file error.vhd
       Expecting : ;
       Found     : else

This error points to the first character of the word else.

jeremiah-c-leary / vhdl-style-guide

Comment tricks vsg into incorrect parsing state #1188