Proposal: Add Comma-separated payloads

[mother10]

As already introduced in PR #552 "SPLAC with PERIODS", this proposal introduces comma-separated payloads.

Some examples:

Specification 1 (inside SPLAC):

  +1 TYPE <Text>                           {1:1}  g71:SPLAC-TYPE 
    +2 HREL <HIERARCHICAL_RELATIONSHIP>    {0:M}  g71:SPLAC-HREL
      +3 GOVTYP  <GOVID_OF_TYPE>           {0:1}
        +4 TEXT                            {0:1}  g71:SPLAC-TEXT  

Without comma-separation:

1 TYPE LOCATION
2 HREL POLI
3 GOVTYP 89
4 TEXT Cemetery

With comma-separation:

1 TYPE LOCATION, POLI, 89, Cemetery

Specification 2 (new STICKY-types in #679 ):

n @XREF:STICKY@ STICKY                          {1:1}  g8:record-STICKY
  +1 TYPE <Enum>                                {1:1}  g8:ENTITY-TYPE
    +2 SUBTYPE <Enum>                           {1:1}  g8:ENTITY-SUBTYPE
    +3 PHRASE <Text>                            {0:1}  g8:PHRASE

Without comma-separation:

0 @ST0005@
1 TYPE ORGANIZATION
2 SUBTYPE MEDICAL
3 PHRASE Hospital

With comma-separation:

0 @ST0005@
1 TYPE ORGANIZATION, MEDICAL, Hospital

Specification 3 (new ROLE-types in #679 ):

  +1 MAINROLE <Enum>                            {0:0}  g8:STICKY-MAINROLE
    +2 ROLE <Enum>                              {1:M}  g8:STICKY-ROLE

This is a special type:

• the MAINROLE has {0:0}, meaning it will never show as it only exists to be able to divide the huge Role table into manageable chunks.
• the ROLE itself has {1:M}, meaning there can be many.

Without comma-separation:

In this case this does not exist, as MAINROLE never shows.

With comma-separation:

1 ROLE MAIN, BRIDE
or
1 ROLE FATHER, BRIDE, PRIEST
or
1 ROLE MAIN, CHILD, ADOPTEE
or
1 ROLE AUNT, WITNESS, GODPARENT