DTSTAMP should be (partially) filtered in calendarDataMatch

[macosforgebot]

douglm@… originally submitted this as ticket:386

---

DTSTAMP is equivalent to LAST-MODIFIED for entities without a METHOD so should be filtered for those tests. For example, tests in put.xml fail because the DTSTAMP value changes,

DTSTAMP from rfc5545:

   Purpose:  In the case of an iCalendar object that specifies a
      "METHOD" property, this property specifies the date and time that
      the instance of the iCalendar object was created.  In the case of
      an iCalendar object that doesn't specify a "METHOD" property, this
      property specifies the date and time that the information
      associated with the calendar component was last revised in the
      calendar store.
...
      In the case of an iCalendar object that specifies a "METHOD"
      property, this property differs from the "CREATED" and "LAST-
      MODIFIED" properties.  These two properties are used to specify
      when the particular calendar data in the calendar store was
      created and last modified.  This is different than when the
      iCalendar object representation of the calendar service
      information was created or last modified.

      In the case of an iCalendar object that doesn't specify a "METHOD"
      property, this property is equivalent to the "LAST-MODIFIED"
      property.

[macosforgebot]

@wsanchez originally submitted this as comment:1:⁠ticket:386

• Radar deleted
• Priority changed from 5: Not set to 2: Expected

[macosforgebot]

@wsanchez originally submitted this as comment:2:⁠ticket:386

• Milestone set to Later