[Uptime] monitor management - adjust sort field map for inline monitor errors

[dominiqueclarke]

Summary

In #130433 we implemented multi fields for some of our monitor saved object properties and implemented sorting based on the .keyword field mapped to type: keyword. This PR adjusts the sortFieldMap to reflect those changes. Without this change, inline monitor errors is broken and monitors will never appear as invalid.

Testing

1. Add the following keys to Kibana.yml https://p.elstc.co/paste/1wHk4Wyl#TsgkPH0nf0Km5FUl0-W2SxbU9WHzIRa2+THKNfyMpar
2. Navigate to Monitor Management. Click Add Monitor
3. Add a browser monitor with the following script

step('Go to https://www.elastic.co/', async () => {
  await page.goto('https://www.elastic.co/');
};

4. Navigate to Uptime. Wait for the monitor result to come back in.
5. Navigate back to Monitor Management. You should see 1 invalid monitor

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[vigneshshanmugam]

LGTM

[justinkambic]

I did create a monitor per the instructions but it did not show as invalid.

[dominiqueclarke]

I did create a monitor per the instructions but it did not show as invalid.

Discussed offline that this is due to an issue with your system clock.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 604f8a8
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
uptime	777.2KB	777.3KB	+50.0B

History

• 💚 Build #39240 succeeded 5185f9f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[shahzad31]

POST FF Testing:
Works as expected, fixes the issue