fix(assetUsage): migrate asset usage table DEV-1013

[duvld]

🗒️ Checklist

1. run linter locally
2. update developer docs (API, README, inline, etc.), if any
3. for user-facing doc changes create a Zulip thread at #Kobo support docs, if any
4. draft PR with a title <type>(<scope>)<!>: <title> DEV-1234
5. assign yourself, tag PR: at least Front end and/or Back end or workflow
6. fill in the template below and delete template comments
7. review thyself: read the diff and repro the preview as written
8. open PR & confirm that CI passes & request reviewers, if needed
9. delete this section before merging

📣 Summary

Use the new table component to display asset usage data. Fixes old pagination issues

💭 Notes

Modeled after how access logs uses the universal table. Removes uid from the AssetWithUsage type as it is not actually expected as a response from backend--updated logic accordingly

👀 Preview steps

1. ℹ️ have an account and many projects
2. submit some data
3. navigate to account/usage > per project total tab
4. 🔴 [on main] notice that pagination doesn't work
5. 🟢 [on PR] notice that pagination does work
6. 🟢 [on PR] notice that table displays the correct data with no regressions
7. ℹ️ have a MMO with different member's permissions
8. 🟢 notice that the table has no regressions related to MMOs

[magicznyleszek]

@duvld you forgot to add task id in PR title :)

[jamesrkiger]

Let's give the table a set height so the sort dropdowns don't get cut off if you only have one asset like here:

This would also make it so the table doesn't jump sizes when you switch from a page of 10 results to a page of 1 result, for example.

Also, there is currently some horizontal overflow, seemingly no matter how wide my screen is. It's fine if there is horizontal overflow on small screens, but can you fix the column sizes so there is no overflow on normal screens?

[jamesrkiger]

Left a couple comments, but it's looking good so far.