Enable groups by default

[otbutz]

The groups feature is still labeled as beta and disabled by default in v1.34.3:

vaultwarden/.env.template

Lines 443 to 448 in 5d84f17

	## BETA FEATURE: Groups
	## Controls whether group support is enabled for organizations
	## This setting applies to organizations.
	## Disabled by default because this is a beta feature, it contains known issues!
	## KNOW WHAT YOU ARE DOING!
	# ORG_GROUPS_ENABLED=false

I couldn't find any open issues mentioned in the env file comment, and it's been working fine for us so far with multiple users, collections and groups.

Maybe it's time to enable it in the upcoming release?

[Ases]

What were the main problems with this feature?

[kpfleming]

Please try to avoid things like "+1" in GitHub issues and discussions; use the existing reactions to indicate your interest in the topic. When you add a comment which says "+1" it generates a notification to everyone that is subscribed.

[uedvt359]

it seems, ases asked a (sensible) question.

i've trawled through issues/commits/prs/discussions, and this is what i found:

#1623 (comment)
#3413

#6017
#3754
#3757

all of them are completed/merged, so i can't see any hold-ups either.

[floriannari]

The latest issues affecting groups appear to have been resolved last July https://github.com/dani-garcia/vaultwarden/issues?q=sort%3Aupdated-desc%20in%3Atitle%20groups
Should groups still be considered “beta”? If so, what are the remaining known issues?