[draft] Feat/serializer context decoupling

[wisepotato]

The main goal of this PR is to counteract the coupling observed in JADNC. Let's make it more testable!

• No more JsonApiContext dependency in Controllers
• The entity is set via ResourceGraph in the middleware now
• no more ApplyContext<T> in the controller, making for a coupling that is not needed
• get all tests working

BUG FIX

• reproduce issue in tests
• fix issue
• bump package version

FEATURE

• write tests that address the requirements outlined in the issue
• fulfill the feature requirements
• bump package version

[wisepotato]

This would also provide a general fix for #251

[wisepotato]

A new controller would like ArticlesController, so no more JsonApiContext.

@milosloub What are your thoughts on this? I would say it makes for a more clean and conscise controller with the resources that it needs, and nothing more, allowing for better testability

        public ArticlesController(
            IJsonApiOptions jsonApiOptions,
            IResourceGraph resourceGraph,
            IResourceService<Article> resourceService) 
            : base(jsonApiOptions, resourceGraph, resourceService)
        { }

[milosloub]

@wisepotato I have to look more into this. This is really big stuff, I have to spend more time to this. Thanks

[wisepotato]

Discussed backward compatibility with @maurei , this will be an afterthought, after fully making what I want I'll try it in one of our V3 projects and see what breaks, and accomodate for that. I'm guessing that's something you would like to see @milosloub 💃

[wisepotato]

Being done in #558