EPIC: TRSS workflow for AQAvit certification

As part of AQAvit certification process, TAP files are collected and put them on a public server. TRSS should be able to get it, parse, store and display the results.

Here is the workflow:
- users register through our API to get a token
- users send us POST request with token, status and URL to the server that contains TAP files, testenv.properties and java -version output(?). Status can be New or Update
- TRSS verifies the token. If it is not valid, an error msg will be returned
- If it is valid, then unzip the zip file and parse the TAP files
- store the information in DB
- display the results on UI (reuse Grid view)

TODOs:

- [ ] [Standardize TAP file name](https://github.com/adoptium/TKG/issues/236)
- [ ] [Set TAP file name Jenkins pipeline](https://github.com/adoptium/aqa-tests/issues/3066)
- [x] #548
- [ ] #579
- [ ] create AQAvit certification API (to take token, status, and URL)
- [ ] create a login page
- [ ] allow users to generate or regenerate tokens
- [ ] create audit links (rerun in Grinder link)
- [ ] TRSS audit logs (for TRSS to keep track user requies)

No implementation files or tests are named. Start by mapping the existing API, token handling, database storage, and Grid view, then review the linked issues and TODO list to define separate work items. Done means the certification workflow is implemented end to end, from authenticated submission and TAP parsing through persistence and UI display.

Written by the indexing model from the issue text.