[9.2](backport #5858) Handle malformatted JSON in .fleet-agents components field

[mergify]

What is the problem this PR solves?

Handles a possible error in loading the model.Agent where the components field might be invalid JSON or a string (due to another bug). This changes the code to be more defensive, also should do less on parsing the components model when that is not needed.

How does this PR solve the problem?

Changes the components field to be a json.RawMessage that does two things. One it stops it from being parsed when the model.Agent is loaded from elasticsearch, which happens often and will reduce the time it takes to parse this field. Two, it stops that field from erroring to be unmarshalled when it is an invalid format.

How to test this PR locally

mage unitTest does a great job of covering it.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

• Closes findAgentByApiKeyId: could not unmarshal ES document into model.Agent: json: cannot unmarshal string into Go struct field Agent.components of type []model.ComponentsItem #5857

  ---

  This is an automatic backport of pull request Handle malformatted JSON in .fleet-agents components field #5858 done by Mergify.

[prodsecmachine]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Licenses	0	0	0	0	0 issues
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.