Add Security page in Reporting docs

[ighristov]

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:

• app configuration settings (assembly and types whitelisting, unsafe mode)
• .trdx / .trdp definitions - guidance to ensure that report definitions come from trusted sources
• type reports in .dlls - guidance to ensure that the .dll comes from trusted sources. For example, a bad agent may use remote code execution
• rate-limiting in Reporting - responsibility of the client.
• data connections must be with the least permissions.
• data fetching can delete info from tables.
• do not include connection strings and credentials in report files
• 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.

[todorarabadzhiev]

https://github.com/telerik/reporting-docs/blob/todor-security/getting-started/installation/security-best-practices.md

[todorarabadzhiev]

Additional resources:
https://testdocs.telerik.com/devtools/document-processing/security/overview

https://supportcenter.devexpress.com/ticket/details/t190349/false-positive-vulnerabilities-known-alerts-detected-by-various-security-scanners-and

https://docs.devexpress.com/GeneralInformation/403365/security/security

https://docs.devexpress.com/XtraReports/119146/reporting-security