[WikiObjectPropertiesListGenerator] Add object's properties code generator for Wiki

[hasecilu]

Replaces #181

Usage:

• Create one object and don't change its default values.
• Select the scripted object on the tree view and execute the macro.
• Mark the checkbox if necessary (it prints "|Dynamic" on the user properties, but not really on use on Wiki pages) and choose the option for the properties you need on your article.
• On the Report View you'll see printed text that you should copy on the Wiki page.

Forum post: https://forum.freecadweb.org/viewtopic.php?f=21&t=61998&start=20
Wiki: https://wiki.freecad.org/Macro_Wiki_Object_Properties_List_Generator

---

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]

Thanks for your contribution!

[hasecilu]

I'll attend the change requests but it got merged before I could make them =/ . fixup! commits are supposed to be squashed to the original commit. I suppose I'll make another PR.

[galou]

I merged because there was nothing blocking it but didn't look at the commits, sorry.

[hasecilu]

I merged because there was nothing blocking it but didn't look at the commits, sorry.

Yeah no problem, generally a good workflow would be that all change requests are done via fixup! commits and I could even comment the hash of the commit on each review to facilitate the review of the changes. After all of that fixup! commits are squashed and you get a clean commit history instead of 5 commits for the same macro.

I think this workflow could be mentioned on the https://github.com/FreeCAD/DevelopersHandbook