ROLIE: Add category to entries

[s-l-teichmann]

Allow parsing of category fields in ROLIE entries.

[github-actions]

Modver result

This report was generated by Modver,
a Go package and command that helps you obey semantic versioning rules in your Go module.

This PR requires (at least) an increase in your module's minor version number.

checking *ROLIEFeed.EntryByID
  in results of func(id string) *github.com/gocsaf/csaf/v3/csaf.Entry
    struct field Base was added to github.com/gocsaf/csaf/v3/csaf.Entry
      Minor

[bernhardreiter]

Comparision of allowed entry elements to what would the code accept with these changes applied:

https://www.rfc-editor.org/rfc/rfc4287

RELAX NG Schema

   atomCommonAttributes =
      attribute xml:base { atomUri }?,
      attribute xml:lang { atomLanguageTag }?,
      undefinedAttribute*
      
   undefinedAttribute =
     attribute * - (xml:base | xml:lang | local:*) { text }

https://www.rfc-editor.org/rfc/rfc8322.html#section-6.2

   atomEntry =
       element atom:entry {
-         atomCommonAttributes,
-		(atomAuthor*
x         & atomCategory*
x         & atomContent
-         & atomContributor*
x         & atomId
x         & atomLink*
x         & atomPublished?
-         & atomRights?
-         & atomSource?
x         & atomSummary?
x        & atomTitle
x         & atomUpdated
x         & rolieFormat?
-         & rolieProperty*
?         & extensionElement*)
     }

• x == exists
• - == missing

[bernhardreiter]

Given the open research question about undefinedAttribute* written down at the bottom if github.com//issues/702#issuecomment-3553564822, my suggestion is that we improve the implementation by adding everything, except undefinedAttribute* and extensionElement and document the open question to resolve.

[bernhardreiter]

LGTM

[bernhardreiter]

We could potentially mention in the docs somewhere that not support undefinedAttribute* and do not support extensionElement .