Add accept header in case of a 415 error

[komape]

Motivation:

Refer to issue #2663 for additional context regarding this PR.

This update introduces an Accept header in the response for situations where an unmatched content type leads to a 415 error. The header specifies the accepted content types following the format outlined in RFC 9110:

<type>/<subtype>; <param_key>=<param_value>

Examples:

• With parameters:

text/html; boo=ya

• Without parameters (only MIME type):

text/html
text/*
*/json

• Parameter present with no value:

text/html; boo

• Multiple accepted content types (comma-separated), which may also include parameters:

text/html, application/json
text/html; boo=ya, application/json

• Multiple parameters for the same content type listed separately:

text/html; boo=ya, text/html; works

• If a parameter value contains special characters, it should be enclosed in double quotes:

text/html; boo="yeah, right"

• If a parameter value contains a double quote, it must be escaped:

text/html; boo="yeah\"right"

This enhancement aims to improve content negotiation and provide clearer guidance to clients regarding acceptable content types.

This PR closes #2663.

[komape]

@tsegismont Seems like the test are executed properly 👍 I'll try to fix the issues.

[komape]

@tsegismont Let me know what you think of the values for the Accept header. The standard for it is not very precise on it and has some leeway in the design. I did what I think is the best but I'm open for opinions 😉

[tsegismont]

Thank you @komape , I went ahead and merged the PR