[Security Solution] Fix success bulk edit toast message

[maximpn]

Resolves: #139897

Summary

Fixes bulk edit success toast's message. Displays You've successfully updated X rules. If you did not select to apply changes to rules using Kibana data views, those rules were not updated and will continue using data views. when rule's index patterns were edited and You've successfully updated X rules. in the other cases.

Before:

Screen.Recording.2022-11-03.at.10.29.25.mov

After:

Screen.Recording.2022-11-03.at.10.28.17.mov

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e7df586

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	3204	3205	+1

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	+2.4KB

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	58	64	+6
osquery	106	111	+5
securitySolution	440	446	+6
total			+19

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
fleet	66	72	+6
osquery	107	113	+6
securitySolution	517	523	+6
total			+20

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

cc @maximpn

[jpdjere]

@maximpn The PR i'm working on extends the API so return if any rules were skipped, so we can inform that precisely. So I think the logic to only show the additional info about data views for index pattern-related actions is not needed.

Take a look and let's align:

#144461

[jpdjere]

Aligned with Maxim that we will get this changes merged first and then apply the changes to the bulk edit API -to include skipped rules in the response- on top of these changes.

That will allow us to display the warning for skipped rules only when rules to be edited were actually skipped.

[jpdjere]

Will modify this logic in #144461 so that the warning that explains that rules with data views were skipped will only show when rules were actually skipped, along with the detail of how many rules were skipped.