CLONED Enable importing DMN object based on MS Excel source file

UseCase:
Business user creates a decision table in MS Excel and IMPORTS it to Business Central as a DMN object (not as DRL / Excel object).

Why? The business people are used to work with MS Excel - and honestly: to create and maintain larger (> 10 columns && > 10 rows) decision tables is far more "smooth"/"efficient" in Excel than in Business Central DMN designer (even after the actual flaws (need to "click" on every cell to edit it; not possible to move across the table using keyboard (TAB)) will by repaired, the user-friendliness of the DMN designer can not surpass Excel).

/*
The as-is DMN module of Business Central can not be practically used: the business users / anaylsts will simply not click-by-click the real-life decision tables in the DMN designer.

an experiment with https://github.com/camunda/camunda-dmn-xlsx din´t work: the import of the "camunda" produced DMN file to Business Central works OK (i.e. one can see and edit the decision table), yet the project CAN´T be BUILT.

*/

Example MS Excel source file attached.