docs: add more context on issue reporting into CONTRIBUTING.md

Add a few more context on issue tracking section, stating the need to always open a issue
when there is no issue created for a future development.

Tracking implementations as issues in github may be very usefull for a free software
context, as it can give more visibility of what is on development and let the others
be able to discuss an implementation even before it starts, making it less likely that
there will be an effort on developing a solution that will not be needed.

Signed-off-by: JGBSouza <[email protected]>
Reviewed-by: Lorenzo Bertin Salvador <[email protected]>
Signed-off-by: Lorenzo Bertin Salvador <[email protected]>

Author: JGBSouza

CONTRIBUTING.md

@@ -192,6 +192,10 @@ Following this practice helps improve project organization and traceability, mak
 
 ## Issue Reporting
 
+We suggest that all bugs, feature requests, and proposed changes be reported as issues. Contributors should create an issue describing the problem or proposal before starting work on a Pull Request.
+
+This approach ensures visibility, provides maintainers and contributors the opportunity to discuss the need and scope of the change, and helps others stay informed about ongoing work.
+
 Use the preconfigured templates on GitHub to report issues and request features. If none of these fit your issue, you can use the "Blank" option.
 
 ## License