fix: incorrect Content-Disposition serialization

[codebytere]

Description of Change

Closes #31662.
Refs #25961.

Fixes an issue where Content-Disposition filenames would be incorrectly truncated at the first comma for filename attachments which contained one. This was happening becuase the filename in the parse net::HttpContentDisposition header was not being correctly wrapped in double quotes, thereby breaking serialization.

Tested with the repro provided in the above linked issue:

Before

After

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixes an issue where Content-Disposition filenames would be incorrectly truncated at the first comma for a filename attachment which contained one.

[deepak1556]

Can you also update the test added in #25961 to also reflect this change ? Thanks!

[codebytere]

@deepak1556 done, thanks!

[release-clerk]

Release Notes Persisted

Fixes an issue where Content-Disposition filenames would be incorrectly truncated at the first comma for a filename attachment which contained one.

[trop]

I have automatically backported this PR to "13-x-y", please check out #31691

[trop]

I have automatically backported this PR to "14-x-y", please check out #31692

[trop]

I have automatically backported this PR to "15-x-y", please check out #31693

[trop]

I have automatically backported this PR to "16-x-y", please check out #31694