Community records: apply `can_community_access` flag for more legacy Zenodo records

[slint]

In legacy Zenodo, community owners could not edit records that were accepted in their communities. This is similar to https://github.com/zenodo/zenodo-rdm/issues/248, but has to be applied for all communities now where the record owner is not the community owner as well.

Will the community curators be able to edit my existing records?

No. You will have to opt-in to allow community curators to edit the metadata of records already uploaded on Zenodo. Metadata of new recods you upload after the launch will by default be editable by curators (and you'll be asked to confirm).

[kpsherva]

the use-case is that:

1. I had a Zenodo record in legacy that is part of a community (that I'm not an owner of)
2. After migration, I don't want community curators to be able to edit my record (even though it's in the community)
3. I can change that via accepting/rejecting the request that is created already

right now there's a flag for permission_flags.can_community_read_files. what's missing is a new flag for permission_flags.can_community_edit so the underlying mechanism is there, but we need a new permission generator we need also to modify the text in the legacy upgrade request to inform about this change in the permissions

[kpsherva]

needs verifying on how many records are affected on zenodo