Questions about tracking upload jobs using using Gaia TAP+

I am running a code that is equivalent to the one in the docs (adding the `job` argument missing in the docs), and I have two questions.

This is the code:
```python
from astroquery.gaia import Gaia

Gaia.login()

j1 = Gaia.launch_job_async(
"select top 10 * from gaiadr3.gaia_source",
name='test',
background=False
)
job = Gaia.upload_table_from_job(job=j1)
```

The call to `upload_table_from_job` returns immediately, but the return value is `None` (whereas from the docs I assumed it would return something). The upload in my actual application takes a while, so I want my script to wait until it is uploaded, but I do not know how to have the script wait. One workaround I thought of is to wait until the table exists.

The questions are:
- How do you retrieve the upload job? It is not returned by `upload_table_from_job`
- The jobs listed by `Gaia.list_async_jobs` never have the name set, so I can't easily identify them, and wonder if I'm missing something. Is there a way to have the job names I see in the Gaia archive web page show up in the `tap.model.job.Job`?

Start by reproducing the documented Gaia.launch_job_async and Gaia.upload_table_from_job example, then inspect how Gaia.list_async_jobs exposes the resulting TAP+ jobs. Determine whether the missing return value and job names are implementation bugs or documentation gaps; done means the upload job can be tracked and its naming behavior is documented or corrected.

Written by the indexing model from the issue text.