UPPSF-6057 category for enriched-content-read-api

[tsvetko24]

Description

• Service enriched-content-read-api adopts the new Go impl. of document-store-api-go.
• This change is adoption in categories, where the enriched-content-read-api service is involved.

What

Add document-store-api-go or replace document-store-api with document-store-api-go in categories where enriched-content-read-api is listed.

Why

UPPSF-6057

Anything, in particular, you'd like to highlight to reviewers

Mention here sections of code which you would like reviewers to pay extra attention to. E.g.

Would appreciate a second pair of eyes on the test
I am not quite sure how this bit works
Is there a better library for doing x

Scope and particulars of this PR (Please tick all that apply)

• Tech hygiene (dependency updating & other tech debt)
• Bug fix
• Feature
• Documentation
• Breaking change
• Minor change (e.g. fixing a typo, adding config)

---

This Pull Request follows the rules described in our Pull Requests Guide

[coveralls-official]

coverage: 65.312%. remained the same
when pulling bdcf9a7 on feature/UPPSF-6057
into b4f5214 on master.

[lokendersinghft]

thought: We are adding this service to more categories than its predecessor document-store-api, which makes sense since the other services in those categories are dependent on document-store.

I assume we will add it to content-read and image-publish when we update the content-public-read and content-ingester respectively.