Add Security page in Reporting docs

DX BU KR: КR4: Public Security Documentation across the products link to the template used in DX BU: Security Article Draft

Create a documentation page that will enumerate the recommended security settings for Reporting projects. Populate the list below with more topics:

[x] app configuration settings (assembly and types whitelisting, unsafe mode)
[x] .trdx / .trdp definitions - guidance to ensure that report definitions come from trusted sources
[x] type reports in .dlls - guidance to ensure that the .dll comes from trusted sources. For example, a bad agent may use remote code execution
[x] rate-limiting in Reporting - responsibility of the client.
[x] data connections must be with the least permissions.
[x] data fetching can delete info from tables.
[x] do not include connection strings and credentials in report files
[x] It is your responsibility to Authorize Reporting REST API - ReportsController. The requests for resources are not authenticated by design
[ ] Web Designer - use https://docs.telerik.com/reporting/designing-reports/report-designer-tools/web-report-designer/customize-web-designer#fine-tune-the-customization-in-the-web-report-designer
[ ] Report Converters - need to explain that the clients need to ensure the reports they're converting to Telerik Reports, are safe.

Statement: if the client extends Reporting engine either with code or with configuration, he is responsible for securing it.