Support *all* item fields

[ecederstrand]

I think it's time to support the kitchen sink. Previous policy was to only add fields that were understood and commonly used, but we have added many new fields since, and now the list of non-implemented fields is somewhat arbitrary and cause for confusion.

For each Item subclass, we should go through the MSDN documentation and add fields to the FIELDS lists with the correct field type and settings. If in doubt, fields should be marked read-only.

[ecederstrand]

After the latest commits, only the following fields are unimplemented:

class Contact:
    UserSMIMECertificate
    MSExchangeCertificate

These are either non-trivial to implement, need proper test data, or throw server errors on my current test server.

[flipdazed]

is Contact.DirectReports related to the OWA contact card Properties that sends a request to {server}/owa/ev.owa?oeh=1&ns=RecipWell&ev=GetRecipProps?

[ecederstrand]

I don’t know how OWA works, unfortunately, so I can’t answer your question.

[ecederstrand]

Contact.photo implemented as a read-only field in f4c2701 It seems like the field is unused and a contact photo should be added as an attachment instead.

[ecederstrand]

#812, #813, #814, #815 and #817 added more fields on Contact, and all remaining fields on Item, CalendarItem, Message and Task.