Project Files Treeview: nit: easy to exclude entrypoint file

[kgartland-rstudio]

Usability nit: the entrypoint can be deselected and deployed. It was harder to deselect it in the previous view because you had to hit the little icon, but now since I can just click anywhere in the filename, it's easier to accidentally add/remove a file.

[dotNomad]

Some of my thoughts:

We currently require the entrypoint to be in the files list. The entrypoint attribute isn't a special include case where the entrypoint file cannot be excluded even if the files list attribute in the configuration is empty.

This behavior makes me want to mirror it in the UI since we are code first, and the TOML code is informing the behavior.

We could require a confirmation, or some other behavior when unchecking the entrypoint. I worry about that a bit since that starts getting into the question of - what else do we require confirmation for. A requirements.txt could also fit into that list, or a renv.lock, but only if Python or R details are included in the configuration file.

---

I try to balance "this is part of the learning curve" and hand holding for complex UIs, and for this in particular I lean toward "this is part of the learning curve".

If we change the behavior of the files include array in the Configuration (to always include the entrypoint, or other files) then I would be more in favor of changing the behavior of the UI.

[dotNomad]

To support disabling and auto-checking the entrypoint (and any other files like the requirements.txt) we need a built in inclusion from the files API.

[dotNomad]

Leaving this out of 1.2.0 until we get outside feedback.

[dotNomad]

Closing this as a duplicate of #1493