[BUGFIX beta] Use notEmpty rather than bool to determine sorting

Previously, when sortProperties is set to an empty array, SortableMixin will
attempt to sort the arrangedContent. With no sortProperties, orderBy() always
returns 0 when comparing two objects. Returning 0 is unstable in some browsers
(I.E. Chrome for arrays with length > 22), meaning the arrangedContent might be
ordered unexpectedly.

Instead, use computed.notEmpty to set the isSorted property. An empty array will
no longer be sorted. When programmatically manipulating sortProperties, it is
easier to maintain sortProperties as an array, rather than setting to null when
empty.

Fix minor typo in test: rearrenge => rearrange
Setup bower canary/beta auto release
Update bin/bower_ember_build with production variables.
Merge branch 'merge-5041'
Update publish script to protect secret.
[BUGFIX] Ensure VERSION_STRING_PLACEHOLDER is replaced in json files
Merge pull request #5042 from rondale-sc/replace_version_string_in_json_files

[BUGFIX] Ensure VERSION_STRING_PLACEHOLDER is replaced in json files
Merge pull request #5016 from kevinkehl/sortable-nonempty

[BUGFIX beta] Sortable nonempty
Close #5051 -- fix validateFullName calls to be assertions
Merge pull request #5057 from kimagure/validateName-assertion

Close #5051 -- fix validateFullName calls to be assertions
Tweak deprecation assertion messages for clarity
Merge pull request #5058 from mixonic/tweak-deprecation-assertions

Tweak deprecation assertion messages for clarity
allow both before and after for initializers
Merge pull request #5063 from simplabs/initializers-before-and-after

Allow both before and after for initializers
[DOC release] Removes statement about `before` and `after` in initializers

Fixes #5061.
Merge pull request #5062 from locks/patch-1

[DOC release] Removes statement about `before` and `after` in initializers
Convert ruby publish to s3 to node
test 1 travis to fire s3 publisher