Refactor usage of .kui* classes in tests

[joshuarrrr]

The only usage I spotted was in this functional test:

OpenSearch-Dashboards/test/functional/services/listing_table.ts

Line 70 in 5b8a378

const links = await find.allByCssSelector('.kuiLink');

It seems like it would be relatively straightforward to add a test id or use another existing class to identify those links.

It may also be worth just migrating/refactoring that test case to https://github.com/opensearch-project/opensearch-dashboards-functional-test as per #2491

[sayuree]

@joshuarrrr So we need to rename existing class and its occurrences, right? Do we still need to migrate it to https://github.com/opensearch-project/opensearch-dashboards-functional-test?

[joshuarrrr]

So we need to rename existing class and its occurrences, right?

Yeah, although it will need some investigation - you may not even need to rename the class if there's another way to reference those elements. Or a test-id may be a better choice.

Do we still need to migrate it to https://github.com/opensearch-project/opensearch-dashboards-functional-test?

Yes, but let's do that in a separate PR. So the first PR will remove the class and update the existing test, and the second PR will be to migrate/recreate the test in the functional test repository.

[Aigerim-ai]

I spotted kui here as well, but I it has its test ID