(DEPRECATED) Bump decidim from v0.29.2 to v0.30.0.rc1

[andreslucena]

This PR updates to the last release candidate version, released yesterday

Mind that there are some changes that need to be handled server-side: https://github.com/decidim/decidim/releases/tag/v0.30.0.rc1

[andreslucena]

@alecslupu I see too many unecessary changes here related to decidim/decidim#13624

Basically there's a mini bug where we're deleting an empty line after the comment with the modification time in the migration files:

Apart from that, I think that we actually should be a bit more honest with the changes here. The logic should be:

• if the files are the same, then don't change them
• If the files are different, then apart from changing the file itself we should actually add a comment just after this line. Something like this:

# This migration comes from decidim_meetings (originally 20210512100333)
# It was last updated automatically during the update process (on 20250219)

I'm seeing the result of this diff and it isn't honest, and it might be a pain to debug in the future (like you only would realize that this migration was changed if you check the diff):

[alecslupu]

Basically there's a mini bug where we're deleting an empty line after the comment with the modification time in the migration files:

Actually, I would say there is no bug. This change is actually coming from #13690, and the code that actually does that, is taken directly from rails's core.
If we look into: 20240619102701_add_valuation_assignments_count_to_decidim_proposals_proposals.decidim_proposals.rb we can see that the # This migration comes from decidim_conferences (originally 20240404202756) is right after the magic comment (# frozen_string_literal: true), but if we check 20240717080147_rename_external_domain_whitelist_to_external_domain_allowlist.decidim.rb, we can see the comment style has been changed.

I would say that we can add that extra comment like:

# It was last updated automatically during the update process (on 20250219)

Between the 2 mentioned files, the Rails upgrade from 6.1.7.6 to 7.0.8.4 happened.

I would say that we do not need to fix this comment

[andreslucena]

Actually, I would say there is no bug. This change is actually coming from #13690, and the code that actually does that, is taken directly from rails's core.

Ahhh ook. Then yeah, if it's already there we can leave it out then!

I would say that we can add that extra comment like:

That'd be great! I think some installations can be bitten by this in the future and if you think that the migration wasn't changed when it was actually changed then it can be pain. To be honest this is something that we should have done each time we changed old migrations upstream too.

[andreslucena]

Closing this one in favour of #142