Environment v3.27.0

Describe the bug For certain very long rule names, e.g. for_generate_statement_502 or case_generate_alternative_501, the standard report produces a table that is not properly formatted. This is because the width of each column in the table is a hard-coded constant, and some rule names are longer than the width of the "Rule" column. Examples:


===============================================================================
File:  test.vhd
================================================================================
Phase 6 of 7... Reporting
Total Rules Checked: 768
Total Violations:    2
  Error   :     2
  Warning :     0
----------------------------+------------+------------+--------------------------------------
  Rule                      |  severity  |  line(s)   | Solution
----------------------------+------------+------------+--------------------------------------
  iteration_scheme_502      | Error      |         13 | Change "IN" to "in"
  for_generate_statement_502 | Error      |         23 | Change "IN" to "in"
----------------------------+------------+------------+--------------------------------------


================================================================================
File:  test.vhd
================================================================================
Phase 6 of 7... Reporting
Total Rules Checked: 769
Total Violations:    2
  Error   :     2
  Warning :     0
----------------------------+------------+------------+--------------------------------------
  Rule                      |  severity  |  line(s)   | Solution
----------------------------+------------+------------+--------------------------------------
  case_500                  | Error      |         15 | Change "OTHERS" to "others"
  case_generate_alternative_501 | Error      |         27 | Change "OTHERS" to "others"
----------------------------+------------+------------+--------------------------------------

To Reproduce Steps to reproduce the behavior:

Create a file called test.vhd with the following contents
```
architecture rtl of test is
```

begin

generate_label : case expression generate WHEN choice => b <= a;

when others =>
  a <= b;

end generate generate_label;

end architecture rtl;

Note that the uppercase `when` will generate an error from the rule `case_generate_alternative_500`.
2. Run `vsg -f test.vhd`.
3. Observe the output

$ ./bin/vsg -f test.vhd

File: test.vhd

Phase 6 of 7... Reporting Total Rules Checked: 804 Total Violations: 1 Error : 1 Warning : 0 ----------------------------+------------+------------+-------------------------------------- Rule | severity | line(s) | Solution ----------------------------+------------+------------+-------------------------------------- case_generate_alternative_500 | Error | 6 | Change "WHEN" to "when" ----------------------------+------------+------------+-------------------------------------- NOTE: Refer to online documentation at https://vhdl-style-guide.readthedocs.io/en/latest/index.html for more information.



**Expected behavior**
I would expect the width of the "Rule" column to adjust dynamically to match the longest rule name in the report.

jeremiah-c-leary / vhdl-style-guide

Report columns are not wide enough for long rule names #1314

$ ./bin/vsg -f test.vhd

File: test.vhd