Fix conversationId comparison bug using integer format

closes #519 (closed)

conversationId is integer string while statusId is a unique alphanumeric string with a fixed length.

Comparison of conversationId is quite buggy.

For example: "10" < "2" (this is valid)

To support proper sorting and pagination, I've converted conversationId to an integer.

added 26 commits

• 0cf3cd23...8e1c5841 - 25 commits from branch pleroma:develop
• 5df71543 - fix conversationId comparision bug using integer format

Compare with previous version

added 3 commits

• 5df71543...4819009d - 2 commits from branch pleroma:develop
• 2b99d92b - fix conversationId comparision bug using integer format

Compare with previous version

added 3 commits

• 2b99d92b...01552d0b - 2 commits from branch pleroma:develop
• a27a2f78 - fix conversationId comparision bug using integer format

Compare with previous version

mentioned in commit 081f9a92

merged