Filter S3 Metadata in COMS data

[TimCsaky]

Description

ticket: https://apps.nrs.gov.bc.ca/int/jira/browse/SHOWCASE-3379

NOTE: we still need to decide on the actual keys we want to exclude. Maybe there's an easy way to update that in future.

general approach:

• remove metadata from the coms response in bcbox service later (object service.getMetadata())
• excluded metadata doesnt get into bcbox store
• if they edit metadata on an object (using bcbox edit metadata form) the new version will not have the excluded metadata
• coms-id tag will always persist
• removed some old code to filter coms-id during update

to test, add this to your local.json and clear browser session storage(existing config):

{
  "frontend": {
    "exclde": {
      "metadata": "geodrive.common.encoding,geodrive.windows.att,geodrive.windows.secdesc,s3b-last-modified",
      "tagset": "coms-id"
    },
    "oidc": {

Types of changes

New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

• may want to consider hiding ugly meta rather than excluding in a future PR
• i think we're duplicating code with searchMetadata() and getMetadata() in the object service.

[github-actions]

Coverage Report (Application)

Totals
Statements:	75% ( 51 / 68 )
Methods:	62.5% ( 5 / 8 )
Lines:	82.61% ( 38 / 46 )
Branches:	57.14% ( 8 / 14 )

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	35.86% ( 616 / 1718 )
Methods:	34.99% ( 134 / 383 )
Lines:	42.94% ( 429 / 999 )
Branches:	15.77% ( 53 / 336 )