Add header support to 3.x->4.x compatibility service

Once we have the initial (and mostly final) implementation of the TK service that handles URL translation, we need to extend it to support header translation.

This is not expected to require much code change to the TK service.

The endpoints+headers that we know are different are:

• node
  • Accept
  • Accept-Encoding
• catalog
  • Accept
  • Accept-Encoding
• file_metadata(s)
  • Accept
  • Accept-Encoding
• file_bucket_file
  • Accept
  • Accept-Encoding
  • Content-Type
• file_content
  • Accept
  • Accept-Encoding
  • Content-Type
• report
  • Accept-Encoding

—

This ticket should specifically take into the account the ability to transfer file content via the "file*" endpoints. This would need to account for the work done in PUP-3812, which changed values in the headers needed for the transfer of "raw binary" files across the "file*" endpoints. Header remapping to preserve file transfer support for legacy clients would likely include:

• Map the Content-Type "text/plain" header to "application/octet-stream".

• Map the Accept "raw" header to "binary".

QA

Risk assessment: N/A: New Feature: Testing organized in SERVER-595 & SERVER-546