Reorder configuration to resolve cucumber mysql errors
Reorder configuration to resolve cucumber mysql errors

We recently started seeing some features fail in
teacher_searches_groups_and_previews_instructional_materials.feature.
The errors were related to database connection sharing between
threads (mysql errors).

I believe the problem started recently when I moved configuration around.
However, it appears these features may have failed in the past too because
some of them have the tag `@with_mysql_failures`.

I believe the problem is that Cucumber::Rails is enacting its own connection
sharing strategy which is similar to ours (same intent) when the configuration
option `javascript_strategy` is set to `transaction`. If our own strategy
(now in the common helper) comes before it, then we have problems.

I tried completely removing the `javascript_strategy` configuration,
unfortunately that's not an option because it then defaults to truncation
which we do not want (and doesn't work at all with seed data).

So, I've opted to reorder some things in cucumbers .env file such that
the order of operations is similar to what it was before these issues
popped up.

concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse