merging cookies is responsibility of the test runner

For some reason, this special logic is only supposed to be executed on
the second request.  For now, we'll extend on recycle, but we should
figure out why this functionality can't be run on every request

Try to avoid making the controller mutate itself so that we can
eventually make the response async

Mocha is already required by AS::TestCase, so remove the duplicate
requires.

remove test/dummy from gitignore when "plugin new -T"

Closes #6920

Examples:

    add_reference :products, :supplier, polymorphic: true, index: true
    remove_reference :products, :user

`add_belongs_to` and `remove_belongs_to` are
acceptable.

Ensure that queued jobs are marshallable

This requires all jobs to be instances of named classes, without block
implementations of methods.

Observer #update refactoring

Jobs pushed to the queue should not contain a reference to it. As the queue
itself cannot be marshalled, and as a consequence of checking the
marshallability of all jobs in the test environment, we can now guarantee this
to be the case in the test environment when using the default TestQueue
implementation.

By marshalling and unmarshalling jobs when adding them to the test queue, we
can ensure that jobs created during test runs are valid candidates for
marshalling, and, thus, that they can be used with queueing backends other than
the default simple in-process implementation.

This will also be used in a subsequent commit to ensure that jobs pushed to the
queue do not contain a reference to the queue itself.

Using an anonymous class prevented marshalling: we're not doing that yet, but
the next commit will introduce this. This also provided an opportunity to
improve the expressivity of the tests and to make the assertion failure
messages clearer.

Don't mark the store as changed if an attribute isn't changed.

Also fix some wrong formatting.

Related discussion:
https://github.com/rails/rails/commit/ab72040b74f742b6676b2d2a5dd029bfdca25a7a#commitcomment-1525256

explains why the file update checker ignores mtimes in the future, plus a little refactor for the same price

Make file name and class name consistant

Related to dbc43bcc

Calculate the seconds since the UNIX epoch using the difference in
Julian day numbers from the epoch date. By reducing the Rational math
to just the offset component this gives a significant improvement.

Benchmark:

Calculating --------------------------------------------
       new     27733 i/100ms
   current     15031 i/100ms
       new     27737 i/100ms
   current     15549 i/100ms
--------------------------------------------------------
       new   548182.1 (±0.9%) i/s - 2745567 in 5.008943s
   current   216380.9 (±1.6%) i/s - 1082232 in 5.002781s
       new   510281.9 (±1.2%) i/s - 2551804 in 5.001525s
   current   219858.3 (±1.8%) i/s - 1103979 in 5.023039s

Introduced in pull request #6910, merged in 2ee3fa1a

connection.tables returns an array of strings

There appears to be a bug with DateTime#strftime("%s") on 32-bit platforms.
Bug report: http://bugs.ruby-lang.org/issues/6683

This reverts commit 210cd756.

Refactor migration test_helper

and create_join_table_test