Fix: Stop asserting an exact total post count in delete_post e2e test (#1621)

delete_post used a hardcoded absolute count ("Current results: 20 /
518") purely as a sanity check that filters were cleared and the
right page loaded. The total is not a fixed fixture value - it's the
live total on a shared test backend, which grows over time as other
automated tests create posts - so the exact match was guaranteed to
drift and fail independent of anything this test actually cares
about (the page size stays 20; only the total changes).

Assert the page-size portion and accept any total instead.


Claude-Session: https://claude.ai/code/session_0142M19Se37Y1pxoNy8HvTKV

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Author: tuxpiper

e2e-testing/cypress/functions/PostsFunctions/PostFunctions.js

@@ -107,8 +107,12 @@ class PostFunctions {
     cy.get(DataViewLocators.revealFiltersBtn).click();
     cy.get(DataViewLocators.clearFiltersBtn).click();
 
-    //verify post count to verify we are in correct post page
-    cy.get('[data-qa="feed-page-results"]').contains('Current results: 20 / 518');
+    //verify post count to verify we are in correct post page. Only the page size (20) is
+    //asserted here, not the total, since the total record count on the shared test backend
+    //grows over time as other automated tests create posts.
+    cy.get('[data-qa="feed-page-results"]').should(($el) => {
+      expect($el.text()).to.match(/Current results: 20 \/ \d+/);
+    });
     cy.contains(this.postTitle).scrollIntoView();
 
     //change post to be deleted to "New Post Title for Location"