Update CODEOWNERS

[adgad]

From a Slack convo - this change hopes to give greater clarity and expectations over ownership and PR reviews for the repo.
The rationale:

• Spark as the overarching owner: the spark team has probably been closest to the setup of the spec and repo, build processes. And it's helpful to have a single team to have accountability over the future direction.
• Content-Team owns the Go stuff (is *.go enough? or should it be something wider, like the folder?
• SPEC.md and package.json (because of version bumps) are co-owned by Spark, Content and Storytelling

(didn't really know what to do with /tests - hopefully this is a good starting point that we can build on)

[apaleslimghost]

thought: as you know, your father, the king @Financial-Times/r13n was the API Rationalisation team; its ownership of cp-content-pipeline was subsumed by @Financial-Times/platforms. it's been rare that we've had a hand in work on content-tree itself but i feel like it's not unthinkable for us to be involved in reviewing things (i'm thinking of things like versioned components or potentially moving some of the model/strategy code into this repo)? 🤷🏻‍♀️

[adgad]

ha, not at all!

I will add to you to the shared list, then future things like models we can cross when we get there

[adgad]

I've also added README.md to that shared list, as I imagine that will encompass any significant changes as well

[andy-little]

Looks like a big improvement to me :)

[todor-videv1]

• go.sum
• go.mod
• content_tree.go
• the libraries folder currently has only go code inside of it

These are the files/folders we should own I think.

EDIT: Ah actually no, the to-string transformer has TS/JS code. @adgad is this code needed, should we delete it like we did for from-bodyxml?

[adgad]

@todor-videv1 have added those extra root files, and the two C&M library folders explicitly

I think we can get rid of to-string - will do that separately