feat(api-tokens): show last usage in token lists

[erebe]

Help users assess token activity directly from organization settings when
reviewing credentials to keep or remove.

Show Last used beside creation details for regular and policy API tokens.
Format the timestamp as a human-readable age relative to when the list
loads, keeping that reference stable across rerenders. Show the exact UTC
timestamp on hover and No recorded usage when the value is null or absent.

Extend the list prop types with optional last_used_at support while the
pinned generated API client does not yet declare the field.

Test relative formatting, placement, hover timestamps, missing values, and
the fixed reference time across rerenders for both lists.

---

Summary by cubic

Shows when API tokens were last used in organization settings so users can decide which credentials to keep or remove.

• Displays "Last used" next to creation details for regular and policy API tokens, formatted as a relative age anchored to when the list loads so it stays stable across rerenders.
• Shows the exact UTC timestamp on hover and hides the field entirely when last_used_at is null or absent.
• Bumps qovery-typescript-axios to 1.1.1011 to declare last_used_at on token types.

^{Written for commit 97cc348. Summary will update on new commits.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 97cc348

Command	Status	Duration	Result
nx run console:build --parallel=3 --configurati...	✅ Succeeded	51s	View ↗
nx affected --target=test --parallel=3 --config...	✅ Succeeded	4m 35s	View ↗
nx affected --target=lint --parallel=3	✅ Succeeded	2m 19s	View ↗
nx-cloud record -- yarn nx format:check	✅ Succeeded	2s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-10-14 12:53:15 UTC

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 9cf22eb

---

☁️ Nx Cloud last updated this comment at 2026-10-14 10:55:33 UTC

[cubic-dev-ai]

All reported issues were addressed across 5 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.12%. Comparing base (78e0baa) to head (97cc348).

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #3107      +/-   ##
===========================================
- Coverage    53.73%   53.12%   -0.61%     
===========================================
  Files         1338     1413      +75     
  Lines        29912    31701    +1789     
  Branches      9130     9411     +281     
===========================================
+ Hits         16072    16842     +770     
- Misses       11308    12214     +906     
- Partials      2532     2645     +113     

Flag	Coverage Δ
unittests	53.12% <100.00%> (-0.61%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[TheoGrandin74]

@erebe Could we also not show anything when there's no usage instead of "Last used: No recorded usage"? It will be easier to scan for those who are actually used that way

[erebe]

Could we also not show anything when there's no usage instead of "Last used: No recorded usage"? It will be easier to scan for those who are actually used that way

Yes that's possible, but a bit deceptive. In the end, after the first usage something will be always displayed.
I can change if you want 🤷‍♂️

[TheoGrandin74]

@erebe I think it's better, if no usage recorded not point of showing it, and visually it will be easier to detect those who were never used VS those we have been used if you need to do some cleaning

[erebe]

@erebe I think it's better, if no usage recorded not point of showing it, and visually it will be easier to detect those who were never used VS those we have been used if you need to do some cleaning

[TheoGrandin74]

@erebe Thanks 🫶
TBH design-wise the best would be to have a real table so you'll be able to sort by creation time/last used that type of stuff, but for now this works well for people asking for it