Improve error handling for web.load when a non-existent task ID is provided.

[FilipeFcp]

A user pointed out that when an incorrect task-id is provided to the web.load function, it leads to a Python error, with a lot of output messages that are not useful for the user.

If possible, a clear message that the task-id doesn't exist could be more informative.

priority: small

[momchil-flex]

What do you think @QingengWei

[QingengWei]

What do you think @QingengWei

Web API returns a 404 NOT FOUND error, but the Python client changes the error to None: https://github.com/flexcompute/tidy3d/blob/develop/tidy3d/web/core/http_util.py#L132-L133

[momchil-flex]

That's funny, who knows where this comes from you or maybe even Lei Zheng in the first days of the web api? Could you propose a change?

[QingengWei]

That's funny, who knows where this comes from you or maybe even Lei Zheng in the first days of the web api? Could you propose a change?

Do you know who they are?

I changed the error code from Web API, and now the error info in Python client is as follows:

[yaugenst-flex]

We should probably just handle status code correctly in the client though I'd say?

[QingengWei]

We should probably just handle status code correctly in the client though I'd say?

I don't know the historical reason. I handle it from the web api and the client does not make any changes.

[yaugenst-flex]

I understand the reasoning, but returning a different error code just to avoid triggering try/except None creates two issues:

1. The frontend still does not handle 404 errors correctly.
2. The web API now returns an incorrect or unexpected status code when a simulation is not found.

Instead of introducing workarounds, we should address the root cause by fixing the frontend to properly handle 404 responses. This ensures both the API and client behave as expected without compromising on correctness.

[QingengWei]

I understand the reasoning, but returning a different error code just to avoid triggering try/except None creates two issues:

1. The front end still does not handle 404 errors correctly.
2. The web API now returns an incorrect or unexpected status code when a simulation is not found.

Instead of introducing workarounds, we should address the root cause by fixing the front end to properly handle 404 responses. This ensures both the API and client behave as expected without compromising on correctness.

From the Python code now, it seems not to care about the error code but the error message. Changing python client code can fix the root cause.