SecurityEntityRiskScore: breaking schema changes + new GET by ID endpoint

BreakingBreaking change

This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.

What changed

Multiple breaking changes to SecurityEntityRiskScoreAttributes and a new endpoint were introduced:

entityID field removed from SecurityEntityRiskScoreAttributes; entityID and entityType removed from the required list, replaced by entityProviders, entitySubTypes, and accountIds as required fields.
SecurityEntityRiskScoreType enum value changed from security_entity_risk_score to SecurityEntityRiskScore — any client matching on this string will break.
New fields added: accountIds, entitySubTypes, entityTypes (additive).
New schema SecurityEntityRiskScoreResponse added for the new single-entity endpoint.
New endpoint GET /api/v2/security-entities/risk-scores/{entity_id} added (additive, still in public beta).
SecurityEntityRiskScoresMeta response example updated with new pagination fields (pageNumber, pageSize, queryId, totalRowCount) replacing page.total.