Object Mapping Strategy

[symorton]

Problem:

• There needs to be a way to map VCSDK data models to the new Wallet Libraries.
• The Services layer in the VCSDK needs to be able to use the built in async functionality instead of PromiseKit.

Solution:

• This PR introduces a Mapping strategy. The new Mapper class maps any object that conforms to the Mappable protocol into a new object.
• By extending VCSDK/VCEntities data models to conform to Mappable, we can use the mapper class to easily map these VCSDK data models to the new ones.
• The Presentation Service was also extended to conform to Presentation Serviceable protocol that uses Swift async functionality to get requests and send responses. A utility class called AsyncWrapper was created to wrap and PromiseKit function in an async function.

Validation:

• Units tests created and all tests pass.

Type of change:

• Feature work
• Bug fix
• Documentation
• Engineering change
• Test
• Logging/Telemetry

Risk:

• High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
• Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
• Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)

Work Item links:
Please include here links for this work item, or deferred work, or related work. E.g. if the refactoring is too big to fit in this PR, or the localized strings need to be updated later, please link the TODO work items here.

Documentation Links:
Please include here links to any related background documentation for this PR.