fix(bg_jobs): store job argument as a text, increase length cap to 32000

[Antreesy]

• Resolves: Background jobs with extended data support > 4000 bytes #58913

Summary

After internal discussion it comes up, that $argument_hash is used in DB queries for references, and $argument should be safe to store as a Type::TEXT. That should allow to increase the max length of JSON encoded string without breaking the DB 🤞🏽

TODO

• Sanity check for changes
• Manual tests
• Decision for backport?

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[provokateurin]

I question a bit why you'd need so much space for arguments, maybe some kind of reference should be passed instead?

[Antreesy]

I question a bit why you'd need so much space for arguments, maybe some kind of reference should be passed instead?

Maybe, but I don't know if that's up to app developers to handle? IIRC and see ref issues, webhook_listeners are expecting to have complete information, e.g. there could be usecases like:

• Tables - table rich text and metadata - we hit the limit here, cc @enjeck
• Talk - supports chat messages up to 32K characters as well - nobody reported such case, but might be possible

To my understanding, current PR would be the less invasive approach to support larger data arrays?

[Antreesy]

/backport to stable33

[Antreesy]

/backport to stable32