Allow development builds and stable builds to be installed simultaneously

[colinkiama]

Problem

When working on elementary Code in elementary Code, you currently need to restart the app whenever you build to see the latest changes.

For people who primarily use elementary Code as their code editor, you lose time restarting the app whenever you would like to preview your changes. Some changes may break the app and will result you in having to use another editor application or revert your changes to get the elementary Code working again.

Proposal

Set the development option in meson to true by default and use a different ID, icon and name to differentiate between stable builds and development builds.

Prior Art (Optional)

GNOME apps for example:

• GNOME Calculator
• GNOME Builder

[jeremypw]

I hard-coded a different app id in the Files Gtk4 branch but this sound more elegant.

[awsdert]

My suggestion for implementing this is for the main executable to be just a thin wrapper that launches the default build. For example: $>code could launch /bin/code which in turn would launch /bin/code-bin/code-rel while $>code --use=dev would launch /bin/code --use=dev which in turn would launch /bin/code-bin/code-dev. Any time you create a release you just make a copy of code-dev as code-rel. No complications as a result.

Edit: For distinguishing between code-rel and code-dev during runtime you could just load /proc/self/cmdline I think it was.