Add option to "Create desktop icon" to Windows installer

[koobs]

Summary

JabRef on Windows automatically installs a Desktop icon during installation, and there is no provision allowing users to not create an icon.

Originally posted by @jorgman1 in #5657 (comment)

Note: icon is currently created in <DRIVE>:Users\Public\Desktop for an administrator permission installation.

Proposal

• Add a checkbox (☑) control option in the Windows installer, that is...
• Enabled (checked: ☑) by default, AND ...
• If checkbox is disabled (☐), do not create a Desktop icon.

Considerations

• For an administrator (permission) shared installation, install icon in %PUBLIC%\Desktop
• For a standard user (permission) non-shared installation, install icon in %USERPROFILE%\Desktop

[AWTemple]

I really like this project proposal. In addition to being software that strikes me as relevant and useful for students, this project also seems, at a glance, to be perfect for the purposes of this class. It’s an open source project with a lot of contributors and momentum, but a long list of known bugs and unresolved issues that demonstrate the project is far from perfect. I believe that, like you said, the open issues or “good first issue” would be a sensible scope for our class project.

I, like many of us, have a decent background in java at this point, which would make this project somewhat accessible to work with. Just glancing over some of the open issues for the project, it seems that many of them are not individually complicated. Perhaps one way to approach this project would be to select a cluster of related open issues to work on all at once, or perhaps picking unrelated ones would be good for experience purposes. Either way, this project strikes me as a really good entry to coding in an open source space.

[koobs]

@AWTemple Agreed.

The gap at present appears to be triaging existing good first issues and ensuring they're in a 'able to take immediate action' state, for example: clear description of feature/issue, clear design proposal ('acceptance criteria'), no open questions

May I suggest creating a meta issue, to identity and list/link (as checkmarks) existing good first issues that the class/students believe that can confidently/comfortably assign (each existing issue) and work on in small, separately committable chunks.