Ruby Feature: Which ruby version manager would you prefer?

Hello! 👋

We are looking forward to get some feedback for refactoring the [Ruby Feature](https://github.com/devcontainers/features/tree/main/src/ruby).

Which Ruby version manager would you like the Feature to install by default? You can use the respective emojis for voting your preference!

1. None - 😕
2. `rbenv` - 🎉
3. `rvm` - 🚀
4. Any other (feel free to drop a comment)

For the ruby Feature, we have heard issues with conflicting ruby managers (`rbenv` and `rvm`) which can be problematic for complex projects. We have a community member who is willing to contribute a PR with the necessary changes ✨ See https://github.com/devcontainers/features/issues/603#issuecomment-1806853742 ❤

### (Draft) Proposal

- Create a new Feature option which will define the ruby version manager to be used for installing ruby
- Let’s say we call it `rubyVersionManager`
- It will be `string` with `enum: ["none", "rbenv", "rvm"])`
- Default value: "TBD: Poll result"
- Based on the value provided by `rubyVersionManager`, the Feature will use that version manager to install ruby
- In case of `none`, we will first attempt to install it with `apt`.
- If it fails, then install from source.

Looking forward to everybody's feedback, thank you!

Leggi prima il Ruby Feature in src/ruby e la bozza della proposta; l’issue richiede una decisione sul gestore delle versioni predefinito e sui valori delle opzioni. Conferma l’esito del sondaggio e la discussione successiva prima di definire l’ambito dell’implementazione; il risultato è una direzione concordata, non ancora una patch specificata.

Scritto dal modello di indicizzazione a partire dal testo della issue.