feat!: use uv instead of poetry for packages management

[pstorozenko]

Tapyr release 0.2

• Default python upgrade to 3.12
• poetry changed to uv
• .gitignore cleanup
• versions bump
• PyShiny -> Shiny for Python rebranding
• Introduce usage of Shiny Testing API instead of raw Playwright
• Change favicon to tapyr
• Extend and improve basic startup tests

[Gotfrid]

LGTM, added a couple of minor comments.

I was able to run the app fine, and the manual deployment went smoothly.

Idea for another PR is to include a module example. Even in shiny docs it's not very easy (i.e. takes >5s) to find how to create a module with separate ui and server.

[Gotfrid]

Another minor thing that I just remembered: it might be good to install rsconnect-python in the devcontainer, or at least mention that it should be installed by the user. why i mention it, is, as you see, pip package name is different from the command.

[f-meister]

Another minor thing that I just remembered: it might be good to install rsconnect-python in the devcontainer, or at least mention that it should be installed by the user. why i mention it, is, as you see, pip package name is different from the command.

I second this. It's not clear in the documentation that you need to install rsconnect separately. Also suggest that they use uv in this case—if I hadn't already known about uv, I would not know that I had to do something like:

uv pip install rsconnect

to install and just do the usual pip install and maybe defeat the whole purpose of having uv ?

[f-meister]

Also LGTM. Just some documentation stuff from me to ensure new users get through the initial process smoothly 😄