[CI] Exclude feature branches from cypress test or change branch fetching

[joshuarrrr]

When it comes to functional tests, we have a chicken/egg problem with new features given the relationship between this repo and https://github.com/opensearch-project/opensearch-dashboards-functional-test. Our current guidance is to add the new feature first, and then add the functional tests. But use of feature branches causes the cypress checkout step to fail:

An example: https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/3849044690/jobs/6557561432

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/feature/feature-anywhere*:refs/remotes/origin/feature/feature-anywhere* +refs/tags/feature/feature-anywhere*:refs/tags/feature/feature-anywhere*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 14 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/feature/feature-anywhere*:refs/remotes/origin/feature/feature-anywhere* +refs/tags/feature/feature-anywhere*:refs/tags/feature/feature-anywhere*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 19 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/feature/feature-anywhere*:refs/remotes/origin/feature/feature-anywhere* +refs/tags/feature/feature-anywhere*:refs/tags/feature/feature-anywhere*

[joshuarrrr]

see opensearch-project/opensearch-dashboards-functional-test#469 for proposed solution.

[ashwin-pc]

I like @kavilla's proposal over excluding the test altogether. Excluding them breaks the main goal of keeping the feature branch on par with the main branch in terms of code quality.