[Export2Slicer] Use step format in export

[dlozinski]

Use step format since Prusa slicer supports step files now.

Thank you for creating a pull request to contribute to FreeCAD-macros!
To integrate your macro please make sure the following steps are complete:

• Please check this box if you're not submitting a new macro.
• Are you submitting a new macro ?
• Have you followed the 'How to submit a macro' section of the README.md ?
• Your macro has a Description in its header.
• Your macro has a CamelCase name.
• Your macro is named appropriately.
• Your macro contains a Metadata section that immediately follows the header description.
• Your macro is Python3/Qt5 compliant and tested on the latest FreeCAD stable and development releases.
• You're including documentation on how your macro works (bonus: screenshots and/or video on the Wiki)
• Commit message is well-written
• Commit message is titled in the following way [MacroName] Short description.
• Optional, write or update the changelog in the macro, from latest to oldest.

And please remember to update the Wiki with the features added or changed once this PR is merged.
Note: If you don't have wiki access, then please mention your contribution on the 0.19 Changelog Forum Thread.

---

[galou]

Why do you think that Prusa's mesher is better than FreeCAD's? I'd guess that it's better to use FreeCAD's mesher because you avoid an intermediate step, in both sense of the word.

[dlozinski]

Why do you think that Prusa's mesher is better

I didn’t say that.

From my experience step worked better - resulted in less errors during import into slicer.

[galou]

Please keep the default format as it was and only add STEP format as an option. Mesh formats are more widely supported.