Rich text handling

[rosemcc]

• Redesigned body media service to build 'global' link maps for resolving data in rich text nodes with linked entries/assets, instead of using the service to manage one rich text field at a time. The solution uses the ngx-contentful-rich-text library as before, but handles the linked data in a better way.
• This addresses the existing problem with handling page types that have multiple rich text fields.
• Removed the no longer needed sub-components of funding and case study pages.
• The BodyMediaComponent which previously handled all the rich text nodes types has been split out into separate components to make it more manageable:
  • BlocksEmbeddedAssetComponent
  • BlocksEmbeddedEntryComponent
  • BlocksQuoteComponent
  • InlinesAssetHyperlinkComponent
  • InlinesEmbeddedEntryComponent
  • InlinesEntryHyperlinkComponent
  • MarksCodeComponent
• The rich text pipe is gone now in favour of only using ngx-contentful-rich-text
• Updated and consistent GraphQL queries for rich text fields.
• Fixed issues with rich text types e.g. inline asset and entry hyperlinks working, handling of internal links.
• Numbered lists are fixed in Firefox
• SVG images can now be used in rich text
• Styling and accessibility improvement for Cards within rich text and fixed issue of images not showing for certain content types
• Replaced markdown-to-html-pipe (no longer maintained) with ngx-markdown
• Empty inline code issue is now handled with custom renderer (MarksCodeComponent)

Ref: https://www.contentful.com/blog/2021/04/14/rendering-linked-assets-entries-in-contentful/

[Trombach]

Nice work, Rose. This is so much better than before! I've added one minor suggestion that you can decide if you want to change it.