Change limit to 535 / 520 for public_info -> store

What does this MR do?

It has been reported that the limit of 180 characters in the public store information is often not sufficient. With the introduction of Markdown, this limit can be reached even faster. In this MR, the database limit has been changed to 535 characters (maximum value of VARCHAR). The limit in the frontend has been changed to 520 characters.

How confident are you it won't break things if deployed?

Links to related issues

https://yunity.slack.com/archives/C74JC2V26/p1726825756166329

How to test

Screenshots (if applicable)

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• set the "API change" label if changes in the API are not backward compatible
• added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
• added an entry to CHANGELOG.md
• added a short text in the release notes to /release-notes/YYYY-MM.md
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
  • Be aware, that also non technical people should understand.