Remove contact data fields from poi

[lunars97]

Short description

Remove contact box(email, phone number and website) from the poi. These fields should be managed in the contacts.

Proposed changes

• Remove contact data from the poi model
• Remove contact data from the poi form
• Migration should be created
• Adjust API so it finds the primary contact of the requested POI and reads those fields from the primary contact
• Remove contact box from poi form
• Adjust test data

Side effects

• none?

Resolved issues

Fixes: #3086

---

Pull Request Review Guidelines

[david-venhoff]

Thanks!
One more thing that this pr needs to handle is migrating the poi fields website, url and phone number to contacts, so that the information is not lost

[MizukiTemma]

We should merge this PR in such a timing that it will be delivered at the same time with (or after) the final release of the contact feature for all users, as this removes the contact fields from POI and they must be then shown as primary contact in the related contact box (which is currently visible only for Service Team and CMS Team).

[MizukiTemma]

Thank you for opening a PR 💪 I have some initial suggestions.

[MizukiTemma]

@lunars97

The box " Contact details" in the POI form must be removed too. After rebasing, a new box with related contacts (introduced by #3162 ) should appear there. Sorry, this was missing in the issue description 🙏

[lunars97]

@MizukiTemma I am receiving test errors, is it because of the test data, specifically, the poi which should not have contact data anymore? 🤔 When I do pre-commit it does not show any test errors...

[MizukiTemma]

@lunars97
Sorry 🙈 I overlooked updates in this branch 🙈

Yes, The three fields should be removed from the POIs of the test data too.

[MizukiTemma]

Thank you so much 😻

Only one suggestion left, which is actually because of the innacurate issue description 🙈 🙏

[JoeyStk]

Thank you very much!
To me this looks very good. I want to double-check the migration in the next days and will do a full review for this PR after :)
For now I have one question: This is maybe for @osmers Is it okay to merge this PR already soon, even before the contact feature is released or should we wait until we merge this until the contact feature is released?
(as a reminder: this PR removes the contact section from pois and adds them to contacts instead)

[JoeyStk]

Except for my question to @osmers I think this looks good. I'm still a bit unsure about the migration, so maybe we can have someone triple-check the code snippet, but other than that I think this looks good :)

[osmers]

I'd wait with merging it - unless we can guarantee that the contact function and this PR will be in the same release. Otherwise where would municipalities write down contact details if this is merged and the contact functionality not yet available?

[JoeyStk]

Blocked until the release of the contact module

[MizukiTemma]

Maybe turn this PR into draft to avoid accidental merge?