feat(testing): add msgpack support

[arthurprioli]

Summary of Changes

Added the msgpack parameter in simulate_request, working in a similar way than the JSON one, when msgpack is not None we pass the content type as MEDIA_MSGPACK and it is fully documented on the comments and documentation.

Related Issues

Fixes #1026.
Relates to #333.

Pull Request Checklist

This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. But please read our contribution guide at least once; it will save you a few review cycles!

If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

• Applied changes to both WSGI and ASGI code paths and interfaces (where applicable).
• Added tests for changed code.
  Added tests in tests/test_testing.py.
• Prefixed code comments with GitHub nick and an appropriate prefix.
  Didn't understand where to put the prefix with my GitHub nick.
• Coding style is consistent with the rest of the framework.
• Updated documentation for changed code.
  • Added docstrings for any new classes, functions, or modules.
  • Updated docstrings for any modifications to existing code.
  • Updated both WSGI and ASGI docs (where applicable).
  • Added references to new classes, functions, or modules to the relevant RST file under docs/.
  • Updated all relevant supporting documentation files under docs/.
  • A copyright notice is included at the top of any new modules (using your own name or the name of your organization).
  • Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
    Didn't understand where to put the versionchanged prefix and if I should put it.
  • Changes (and possible deprecations) have towncrier news fragments under docs/_newsfragments/, with the file name format {issue_number}.{fragment_type}.rst. (Run towncrier --draft to ensure it renders correctly.)

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

PR template inspired by the attrs project.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a54317c) to head (97b52c8).

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #2394   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         7861      7867    +6     
  Branches      1076      1077    +1     
=========================================
+ Hits          7861      7867    +6     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[CaselIT]

looks mostly fine, thanks!

The only comment that needs to be solved is the docstirng one

[vytas7]

Hi again, and thanks for this pull request!
I think it is a great start, but it still needs work to bring it out from Draft (that I've just converted it to), and later to merge it.

(See the inline comments.)

[vytas7]

@arthurprioli thanks for your work on this so far.
Unfortunately, this PR still has much work left (see the inline comments) in order to bring it to the point where we can merge it. Do you intend to continue work, or can we close it for the time being? We are trying to get our PR backlog under control.

[arthurprioli]

Hello @vytas7, sorry for taking too long to answer. But can I still work on this PR? I had a bit of a messy end of year and didn’t have much time to finish it, but now I have more free time so I could wrap it up.

[vytas7]

Yes @arthurprioli, no worries, you can still work on it 🙂

[arthurprioli]

Hello @vytas7 , sorry for coming here after such a long time, but I was wondering, this blocked by release tag means it is not an issue anymore? And if you need changes, what can I improve on it?

[vytas7]

Hi @arthurprioli, and welcome back!
There is no such tag on this PR anymore -- it is a temporary measure to suspend merging new features under the beta testing phase of an in-tree release, or when a change needs to wait for a newer release.

In any case, it should not concern You, the contributor. The only effect to you is that the PR might get slightly delayed.

[vytas7]

@arthurprioli regarding the proposed changeset, let us take a fresh look at this again after a long time.
(I thought that this was still awaiting changes from you, but maybe it is not the case any longer.)

[vytas7]

See my comment about the parameter order inline.

Also, we need to address the merge conflicts.

[arthurprioli]

Hello, @vytas7, sorry to bother, I think I finished this PR, just placed the msgpack parameter as last parameter and fixed the merge conflicts.

[vytas7]

Thanks @arthurprioli! We'll take a look.