Address Activity properties in schema_manager

[maxsibilla]

Related to #606

• schema_manager specifically in any of the normalize functions
  • We have to add protocol_url to properties_to_include since these functions work strictly off of the provenance schema

[libpitt]

Currently the filter_properties feature query returns any requested property name clashes between Entity and Activity with an appended prefix activity_.

To this date's implementation, any clashed requested properties will only return the ones for Entity in the response.

When reworking the method normalize_entities_list_for_response, if needed to include both of such clashed fields, would need to consider this scenario in order to return the clashed fields for both Activity and Entity in the response.