fix: catch exceptions for get_table

[mekhlakapoor]

The flow was updated to properly propagate an error. This PR updates the get_table route toraise when an exception is caught NotFoundException is caught.

Question:

• Is this handling necessary? None of our other microservices are explicitly handling errors.
• Other microservices return [] when queried "badly" (ex: smartsheet/perfusion/bad" returns []) so first pass of this PR caught the NotFoundException and returns an empty list. However handling it like so (especially for fetching a table) is ambiguous

[helen-m-lin]

Returning [] could be ambiguous for cases where table exists but is empty.

Instead of only handling NotFoundException, would it make sense to catch all PowerPlatform exceptions?

except allen_powerplatform_client.exceptions.ApiException as e:
    raise HTTPException(
        status_code=e.status,
        detail=e.reason,
    )

[mekhlakapoor]

I agree that it could be ambiguous. However none of our other services have explicit error handling / raise HTTPExceptions in the server routes. I believe we did this on purpose to keep things simple but I may be misremembering.

I've updated the branch to propagate PowerPlatform exceptions because I do agree that having the actual exceptions could be useful but would be open to your thoughts @jtyoung84

[jtyoung84]

That should be fine.