chore: transformer 404 error logs

[vinayteki95]

Description

This commit aims to allow logging of 404 errors in the processor while communicating with transformer to trigger log based alerts (loki)

Transformer can respond with 404 errors if the destination is not available in the transformer image but the config-backend has the destination.
This can only happend when some outdated transformer image is used in the deployment. In order to catch such errors and immediately alert (throw loki-log based triggers) the team to make a fix, we aim to log 404 errors and add alerts for those errors.
The below ticket is attached with corresponding alert PR in devops as well.

Linear Ticket

Resolves INT-3031
https://linear.app/rudderstack/issue/INT-3031/revisit-transformer-and-rudder-server-api-contracts-and-throw-alerts

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.85%. Comparing base (cd4a7e1) to head (0427544).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5437      +/-   ##
==========================================
+ Coverage   74.82%   74.85%   +0.03%     
==========================================
  Files         440      440              
  Lines       61668    61668              
==========================================
+ Hits        46141    46164      +23     
+ Misses      12991    12960      -31     
- Partials     2536     2544       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[utsabc]

Can you add some more context in the description?

[vinayteki95]

@utsabc Updated the description with more details. Good catch, this PR is very vague without the context.