Maintenance: Rename ServiceError to HttpError in REST API

[svozza]

Summary

In #4602, as part of the discussion there was a suggestion that the name ServiceError is confusing due to the similarity with InternalServiceError. A suggested and more accurate alternative is HttpError.

Why is this needed?

The name HttpError is more descriptive of what the error represents.

Which area does this relate to?

No response

Solution

Rename the abstract class and update all references to it in the codebase.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.