Api for node report headers(#5669)

[mchengat88]

🔩 Description: What code changed, and why?

Adding new API(V1) to get the node information to be shown on UI

⛓️ Related Resources

#5669

👟 How to Build and Test the Change

Clone the updated codes.
Rebuild automate-gateway and compliance-service
Curl new api
curl -X POST -H 'Content-Type: application/json' -H 'X-Data-Collector-Auth: version=1.0' -H 'X-Data-Collector-Token: xxx' https://a2-dev.test/api/v1/compliance/reporting/nodeheader/id/8b7ad6a1-778e-4670-a071-6fd27ca22645 -k --silent -d '{"filters":[{"type":"start_time","values":["2021-09-17T00:00:00Z"]},{"type":"end_time","values":["2021-09-17T23:59:59Z"]}]}' | jq "."

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[kalroy]

Please modify the way the API is exposed and handled in gateway.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

40.0% Coverage
5.6% Duplication