Add more properties to the 'DocumentSummaryInfo' PropertyIdentifiers set

[Numpsy]

Adds more properties listed at https://learn.microsoft.com/en-us/openspecs/office_file_formats/ms-oshared/3ef02e83-afef-4b6c-9585-c109edd24e07

As an example, structured storage explorer currently shows the properties in this file with two numerical identifiers as property names

but afterwards they all have a name:

[jeremy-visionaid]

Generally as a wider point when looking at this code, it seems to me like all the things for a property set should be encapsulated together rather than some bits as a ContainerType and some in PropertyIdentifiers and perhaps expose some kind of registry for additional sets. Since other property sets are possible, it doesn't seem particularly extensible as is... But that's probably something for another day and another pull request.

[jeremy-visionaid]

Should CodePageString also be updated to PIDDSI_CODEPAGE? And similarly PIDSI_CODEPAGE for SummaryInfo?

[Numpsy]

I don't know what the historical reason was for it being different, but the new major version seems like the right time to change it if wanted

[Numpsy]

it doesn't seem particularly extensible as is

It's a bit painful because there are some special cases where you really need specific knowledge of a property set to process everything correctly - e.g. the situation with aligned/unaligned strings which both have the same property type.

Allowing callers to provide their own property factory might be one way of handling that, but the API would need some thought.

Really I don't know if OlePropertiesContainer should try to do full processing of arbitrary streams ('AppSpecific;') or if there should be one or more focussed types at the top level, with a more generic layer underneath as building blocks for users to build their own containers on.