No validation for a too long name in Profiler Captures List exists

Steps to reproduce:

1. Create and open a new project
2. Open Window -> Analysis -> Profiler
3. Enter Play Mode and record some profiler data
4. Save the data
5. Rename the captured data to a 244-character-long name (below the warning limit)
6. Observe the Profiler

Actual results: The Capture data card fails to display in a working manner (Target FPS is hidden, CPU/GPU is hidden, generic tooltip is hidden), and a "Failed to write highlights data to file" error is thrown

Expected results:

• The Capture data card displays data as usual (Target FPS shown, CPU/GPU target shown, generic tooltip shown) and no error is thrown; or
• A dynamically calculated warning about a too-long name is shown, invalidating the name

Reproducible with versions: 6000.3.16f1, 6000.4.9f1, 6000.5.0b10, 6000.6.0a6

Can’t test with versions: 6000.0.76f1 (No Captures List on the left)

Tested on (OS): Windows 11 Pro (25H2)

Notes:

• The path length up to 260 characters is supported for .highlights and .data files in Profiler
• If the name itself (not the path) is >244 characters long, a warning is thrown, however the complete path to the profiler captures is usually longer than 15 characters, so the bug can be reproduced on a much shorter name than 244 characters