Fix Regex string in API middleware to properly match against page
The current regex string will match against params like
per_page as well as
page which creates an issue if the
per_page comes second. As it will grab the latest value when lazy matching. To fix, we need to ensure values '?' or '&' directly precede the word 'page'. This guarantees it matching only with the param 'page'