check digrams with flow for changes

[arhimede]

Bug Report

Q	A
Version(s)	6.0.0

Summary

documentation and website dotkernel.org
@alexmerlin please check all diagrams and see which one need to be update
to reflect the version 6 structure and flow

How to reproduce

Expected behavior

[alexmerlin]

Replaced screenshot in v6/introduction/file-structure/ via dotkernel/api-documentation#116

[alexmerlin]

@bidi47 I don't have the image template for these diagrams, can you regenerate them based on my notes below?
Then replace them in dotkernel/dotkernel.github.io/tree/main/img/api/v6

The Middleware Flow page

I recommend that we take the list of middleware from the pipeline file.
I would remove the Other middlewares (Optional) sections and replace them with the actual middleware names, because we want to showcase the middleware we use in Dotkernel API.
First of all, they are not optional.
Second, telling devs that there are more middleware without clling them out adds no value to that diagram.

The Default Library Flow and Library Flow for Email pages

We need to change the following:

Request
dotkernel/dot-errorhandler
mezzio/mezzio-cors

to:

Request
mezzio/mezzio-problem-details -> dotkernel/dot-errorhandler
mezzio/mezzio-cors

Other than this, the flow is pretty much the same.

[bidi47]

please review this PR for the new screenshots
dotkernel/dotkernel.github.io#37
and this one for the updated pages on dotkernel.org (the source for the screenshots)
dotkernel/dotkernel.org#30

[arhimede]

please review this PR for the new screenshots dotkernel/dotkernel.github.io#37 and this one for the updated pages on dotkernel.org (the source for the screenshots) dotkernel/dotkernel.org#30

@alexmerlin