Client: refactor ReferenceSegment

[me-andre]

Description

As a developer I want readable code

Acceptance criteria

• [ ] Should be maybe just created from scratch, it's hard to tell how it works by looking at the code
• [ ] The references API should be consistent. CreateProfileInput has the property referencesData renamed to references.
• [ ] Users should be able to create references with the same name (confirm with product team)
• [ ] Users should not be able to submit references without url (confirm with product team)
• [ ] On delete references cache is updated (open edit dialog > delete a reference > close dialog > open it again, doesn't show the old deleted reference).

Additional Context

• It has multiple notes and todos from multiple devs who saw this code since it was created in 2021.
• For the communityGuidelines template library I ( @ccanos ) had to create FormikReferencesSegment, there was already a ProfileReferencesSegment. Then they use ReferencesSegment which is a FieldArray with a weird API (push and remove callbacks) which makes things quite difficult. We need to refactor these.
• At the moment, when we are editing an entity, we do have a profile where we can upload references, when we are creating a new entity, that profile (and it's storageBucket) still doesn't exist, so any upload to a reference while creating an entity ends up in the space's StorageBucket or failing.
• Another problem we have at the moment is, if you create 3 references for example, they'll have names 1, 2 and 3. You delete the 2nd, so you have 1 and 3. Then you can't create another one (you get an error), because the name "New reference (3)" is already taken. We think should allow references with the same name.

Areas that will be affected

To be added during the refinement

[ccanos]

@me-andre I have added a few notes more, feel free to correct anything

[techsmyth]

And we should be able to add references on the client before creating the actual reference, avoiding the create / delete cycle. It will mean using another, temporary storage bucket for the uplaod + moving the document storage afterwards