feat(@dpc-sdp/ripple-tide-search): allow multiple result items types

[lambry]

What I did

• Add support for multiple result item types, the search listing API/JSON looks like this would be supported, plus why not support it.

As an example say you wanted something like a News & Events listing, the example config below is now supported.

"resultsConfig": {
    "layout": {
      "component": "TideSearchResultsList"
    },
    "item": {
      "news": {
        "component": "TideNewsSearchResult"
      },
      "event": {
        "component": "TideEventSearchResult"
      }
    }
  }

Checklist

For all PR's

• I've added relevant changes to the project Readme if needed.
• I've updated the documentation site as needed.
• I have added cypress tests to cover my changes (if not applicable, please state why in a comment)

For new components only

• I have added a story covering all variants
• I have checked a11y tab in storybook passes
• Any events are emitted on the event bus

[netlify]

✅ Deploy Preview for ripple-docs canceled.

Name	Link
🔨 Latest commit	ae054e8
🔍 Latest deploy log	https://app.netlify.com/sites/ripple-docs/deploys/665d3aebdb2cba000853aa3a

[dylankelly]

Might be useful to discuss whether we could support different results based upon other properties instead of content type. For example, what about data pipelines that include different results based upon arbitrary fields? What if we had a way to pass a function to determine what result type to use?