chore: Export act from utils

[georgylobko]

Issue #, if available:

Description of changes:

After exporting act from DOM utils, it turns out that after rewriting the import path from @cloudscape-design/.../dom to @cloudscape-design/.../selectors, act remains in the import statement, which is not expected.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.60%. Comparing base (7c63f39) to head (78084f2).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   93.60%   93.60%           
=======================================
  Files           5        5           
  Lines         266      266           
  Branches       58       58           
=======================================
  Hits          249      249           
  Misses         17       17           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[just-boris]

Or you could export act from @cloudscape-design/test-utils-core/utils and avoid this dom/selectors duality

[georgylobko]

Or you could export act from @cloudscape-design/test-utils-core/utils and avoid this dom/selectors duality

I considered this option, but decided to keep there, because act belongs to dom operations.

[just-boris]

Manipulating source code is more hacky operation than using a different file for import.

One may also argue utils.ts is a good place for dom operations, because KeyCode is already there and it is a DOM operation too:

test-utils/src/core/utils.ts

Line 70 in 7c63f39

export enum KeyCode {