Fix updating no of post after deleting a post and load-more button

[individual-it]

This pull request makes the following changes:

• fixes updating the post counter when deleting a post
• loading the correct amount of posts when a post was deleted and then more posts are loaded
• UI end-to-end test infrastructure with tests for the fixes in this PR

Testing checklist:

• 22 Scenarios about deleting posts and showing more posts, see .feature files in this PR. All tests are implemented in CI and are passing, see E2E test infrastructure #1473

• I certify that I ran my checklist

Fixes ushahidi/platform#3861 & ushahidi/platform#3326

Ping @ushahidi/platform

[ushbot]

Hey @individual-it,
thank you for your Pull Request.

@rjmackay It looks like this brave person signed our Contributor License Agreement. 👍

Always at your service,

clabot

[individual-it]

I'm leaving the commit history for now, just for reference. I can squash them when the responsible people are happy with the changes

[individual-it]

fixed conflicts that appeared because of #1443.

[phil-davis]

In one of the feature files there could be a scenario that first pages down into the middle of many posts, and then deletes a post.

And also page down to display all posts and delete the very last post (I guess that will need the "many posts" to have different titles so you can uniquely find the last post)

[individual-it]

The issue is, that the order of posts is random

[individual-it]

@phil-davis I've addressed your requests

[phil-davis]

LGTM

[rowasc]

hey @individual-it. Thanks for your contribution. As I see this, the change should not include a completely new testing framework to be included. I encourage you to use the testing setup that is already here.
I would like to discuss the possibility of adding nightwatch since it's a great tool, but that should be done in a separate PR to ensure we handle it as a separate decision.

Thanks!
Romina

[individual-it]

@rowasc I've added the tests to make sure the fix does fix all cases for the user, specially because at the beginning there have been kind of two separate issues.
But you are right the whole test-setup can go into a separate PR, I will pull it our

[individual-it]

This PR now only contains the fix, the UI tests are moved to #1473

[Angamanga]

This works fine! Thank you so much for your contribution 🎉