More ergonomic and consistent ActionEntityBuilder

[Pfeil]

• make type mandatory
• differentiate between add and set
• provide convenience methods to add a single item multiple times so we can avoid creating lists all the time
• consider using a set instead of a list to avoid duplicates?
• Javadocs to explain that some methods append a single item to the list/set
• make private attributes protected
• fix linter hints in affected files
• fix test coverage

---

As I am at this section anyway, let's do a small spec check:

• Check if we support this: https://www.researchobject.org/ro-crate/specification/1.1/provenance.html#digital-library-and-repository-content
  • Should work, but we do not have a convenience class or builder for all of it.
• check attribute enforcement
  • "Actions MAY have human-readable names, which MAY be machine generated for use at scale."
  • "A curation Action MUST have at least one object which associates it with either the root data entity Dataset or one of its components."(The spec examples violate this, so we do not enforce it in a hard way)
  • "An Action SHOULD have a name and MAY have a description."
  • "An Action SHOULD have an endTime, which MUST be in ISO 8601 date format and SHOULD be specified to at least the precision of a day."
  • "An Action MAY have a startTime meeting the same specifications."
  • "An Action SHOULD have a human agent who was responsible for authorizing the action, and MAY have an instrument which associates the action with a particular piece of software (for example, the content management system or data catalogue through which an update was approved) which SHOULD be of @type SoftwareApplication."
  • "An Action’s status MAY be recorded in an actionStatus property. The status must be one of the values enumerated by ActionStatusType: ActiveActionStatus, CompletedActionStatus, FailedActionStatus or PotentialActionStatus."
  • "An Action which has failed MAY record any error information in an error property."
  • "To record curation actions which modify a File within a Dataset - for example, by correcting or enhancing metadata - the old version of the File SHOULD be retained, and a CreateAction added which has the original version as its object and the new version as its result." (Not sure if we can support this somehow in the API or give a warning triggered by indicators?)

[coveralls]

Pull Request Test Coverage Report for Build #206

Details

• 33 of 33 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 89.935%

---

Totals
Change from base Build #200:	0.2%
Covered Lines:	1519
Relevant Lines:	1689

---

💛 - Coveralls