feat(image_decoder): add stride warning

[FASTSHIFT]

Description of the feature or fix

Using width to calculate stride will lead to very difficult consistency problems.
We should remind users to set the correct stride information in the decoder.

Notes

• Update the Documentation if needed.
• Add Examples if relevant.
• Add Tests if applicable.
• If you added new options to lv_conf_template.h run lv_conf_internal_gen.py and update Kconfig.
• Run scripts/code-format.py (astyle needs to be installed) and follow the Code Conventions
• Mark the Pull request as Draft while you are working on the first version, and mark is as Ready when it's ready for review.
• When changes were requested, re-request review to notify the maintainers.
• Help us to review this Pull Request! Anyone can approve or request changes.

[FASTSHIFT]

We need to update all image resources inside lvgl, otherwise a large number of warning logs will be generated.

[kisvegabor]

For the current demos I suggest adding the stride by hand. It might be complicated to generate the images automatically due to special cases like

• Set special color format
• We might want to convert one image assets in multiple formats.

[kisvegabor]

We need to update all image resources inside lvgl, otherwise a large number of warning logs will be generated.

Due to this IMO we shall update the strides in the PR too.

[kisvegabor]

What about this?

We need to update all image resources inside lvgl, otherwise a large number of warning logs will be generated.

[FASTSHIFT]

What about this?

We need to update all image resources inside lvgl, otherwise a large number of warning logs will be generated.

I used a script to automate the resource changes: #5653

[FASTSHIFT]

Considering that the decoder has not been fully adapted, first reduce the LOG output level.