Clean up after the homepage builder work

[sebastienhoorens]

This is a cleanup PR which we'll release in January 2024 (to have some time to be able to revert to the old homepage in case a customer is very unhappy with their new homepage). Review is therefore not urgent.

• Homepages are no longer needed and are completely removed.
• Removed the old craftjs_jsonmultiloc attribute from the layouts.
• We noticed that pins are not used anywhere and removed those as well.
• The homepage_builder flag is removed, as we completely switch to the new homepages.
• The currently_working_on_text is no longer used.
• Some last small fixes, like the sanitization of text in craftjs_json.

[cl-dev-bot]

	Warnings
⚠️	The changelog is empty. What should I put in the changelog?
⚠️	The PR title contains no Jira issue key (case-sensitive)
⚠️	The branch name contains no Jira issue key (case-sensitive)

	Messages
📖	Run the e2e tests
📖	Check translation progress

Generated by 🚫 dangerJS against f48808b

[jamesspeake]

All looks well tidied to me. Just a couple of comments

[jamesspeake]

Not entirely clear what's happening here, but given it is setting columns to null, just want to check there is no need for that data any more.

[sebastienhoorens]

This is because the homepage was deleted, so the layouts linked to homepages can no longer reference them.

[jamesspeake]

Would this be better as an if/else or ternary as surely any other parameter of content_buildable will return nil too?

[sebastienhoorens]

I'm considering it tech debt, but the report builders should also be supported through this endpoint. I don't have a very strong preference, but I think it can be good to explicitly list all the expected content_buildable types (for example, here you can see that the report builders are (probably) not yet supported because they are not a part of the case statement).