[WIP] Add support for direct rendering from Report class

[Copilot]

• Add Export method to Report class that saves to file
• Add ExportToMemory method to Report class that exports to byte array
• Add support for passing parameters directly via IDictionary parameter
• Create comprehensive unit tests for Export functionality
• Create a simple example demonstrating the Export functionality
• Test and verify functionality manually (CSV and XML exports work correctly)
• Run security scanner (CodeQL)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add support to directly render from Report class</issue_title>
<issue_description>The report class should be able to be used directly to create reports and export to pdf/excel/etc... if the program does not need to display on a viewer.

Provide an example in the wiki how to do this and if there are any code changes required make them.

Also include support for direct parameters on Report class. See #47 for an example of how they should work.
</issue_description>

Comments on the Issue (you are @copilot in this section)

@majorsilence @kobruleht I am going to be very busy until the weekend. I'll review everything then. @majorsilence Go ahead and post your changes here and I can review them.

What I was thinking is to add a new function called Export to the Report class.

RdlCmd.cs has the function SaveAs. I'd like something like this directly in the Report class so I could do

Report rpt;
// do stuff
rpt.Export(PDF, SavePath);

@majorsilence I have not tested this yet. I have been short on time. I'll try to review it tonight.

The ability to save report to memory without creating a file is also very welcome.

Fixes #48

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.