[Security Solution] Fix rules table refresh after rule's import

[maximpn]

Resolves: #136758

Summary

It fixes the problem of the rules table refresh after importing a rule.

Before:

Screen.Recording.2022-11-01.at.21.14.58.mov

After:

Screen.Recording.2022-11-01.at.21.18.10.mov

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[maximpn]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 2a20e65

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
securitySolution	9.6MB	9.6MB	+64.0B

Unknown metric groups

ESLint disabled in files

id	before	after	diff
osquery	1	2	+1

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
fleet	57	63	+6
osquery	103	108	+5
securitySolution	439	445	+6
total			+19

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
fleet	65	71	+6
osquery	104	110	+6
securitySolution	516	522	+6
total			+20

History

• 💛 Build #84512 was flaky e3ede7a
• 💚 Build #84470 succeeded 9f7014f

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

cc @maximpn

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[maximpn]

@banderror @xcrzx AFAIK we have file structure changes and usage of React Query hooks since starting from 8.6 so back-porting does't look safe here. WDYT?

[banderror]

AFAIK we have file structure changes and usage of React Query hooks since starting from 8.6 so back-porting does't look safe here. WDYT?

@maximpn ++, I guess backporting would require fixing it from scratch in 8.5, I'd not spend time on that

[xcrzx]

Haven't tested locally, but the code changes LGTM 👍