Exclusion of Simova document entries when cloning production environments

Problem:
- When copying a Business Central production environment to a new sandbox environment, all Simova table data is included, including document entries and their metadata.
- These document entries are bound to the repository configured in the production environment, making them inapplicable in the new sandbox environment which has its own repository.
- This results in errors when accessing the document entries through the datagrid.
- Deleting these document entries is time-consuming, especially in customer environments with a large number of document entries (current examples range from 500,000 to 2,000,000, taking a day or more to delete).

Desired Solution:
- Exclude document entries and all related data when copying a Business Central production environment to a new sandbox environment.