Suite: Check generated codes against nullable warnings #15124
Description
Resolves #15062
Instead of using nullable warning pragma, we should use null! (null-forgiving operator) for suppressing possible nullable warnings.
Checklist
- I fully tested it as developer / designer and created unit / integration tests
- I documented it (or no need to document or I will create a separate documentation issue)
- I worked with the design team to get their idea for UI/UX design (or no need to design for this PR)
- I've assigned reviewer, related labels and set a milestone for this PR
How to test it?
Run Suite, generate entities, set WarningsAsError and TreatWarningsAsError to true in csproj files of domain, application, application service, entity framework projects (as shown here) and, build the application. It should not give any error related to warnings.