fix overflow issues on metrics table

[mayberryzane]

Summary

• fixes issue where header could overflow (use ellipses and hide overflow when there are way too many cells)
• fixes issue where header/rows could wrap to multiple lines
• set a min-width on the first column so timestamps are always fully visible
• fixes issue where an overflowing table would cause funky dashboard grid sizes
• add empty state
• fix helmets and remove autocomplete
  https://www.loom.com/share/2c74bffe247343c4a63a5bad915b75ac
  https://www.loom.com/share/b1b49e18da3542db8fec8b7c21897509

How did you test this change?

• clicktested locally

Are there any deployment considerations?

• no

Does this work require review from our design team?

• @julian-highlight

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6aba9e8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "rrdom" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrdom-nodejs" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrweb" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrweb-player" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrweb-snapshot" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@rrweb/types" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@rrweb/web-extension" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrvideo" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[greptile-apps]

Pull Request Summary

• Overflow Fixes: Implemented solutions to prevent overflow and wrapping in the metrics table's headers and rows, enhancing UI stability.
• Column Visibility: Ensured the first column's minimum width is set, keeping timestamps fully visible and improving data readability.
• UI Integrity: Adjustments made to address funky dashboard grid sizes caused by an overflowing table, aiming for a more consistent and user-friendly layout.

Potential Pitfalls and Notes

• Styling Impact: Ensure the CSS changes do not negatively impact other tables or components with shared styles, to avoid unintended layout shifts.
• Code Reuse: Opportunities for code reuse in similar components might arise, promoting consistency across the platform.
• Design Review: Awaiting feedback from the design team to confirm these changes align with overall UI/UX goals.

[Vadman97]

preview looks great