[maven-release-plugin] prepare release broadleaf-3.1.0-M2
[maven-release-plugin] prepare for next development iteration
#641 - Provide the ability to hide/show the ID column on list grids
Cherry picked from BroadleafCommerce-3.1.0-GA
Fixes #620 and finalizes #429 - Remove outdated merge cart service invocations by deprecating the merge cart processor as it has now been moved to the cart state processor. Also, remove any anonymous customer session attributes after their cart has been merged

(cherry picked from commit 1a6d6be66f52087fa0cf544aa5aa8416da867475)
Fixes #639 - Automatically filter archived entities in the admin. Also default Persistence event handler methods to default to not handled so that subclasses only have to override what they need to

(cherry picked from commit 8493a97902b81a0c7c04c56aaf142a727cf7e4d4)
update config for 3.1
Revert: update config for 3.1 (baa96a08d0a0cf736f16a3ad9f1d81273d0400d5)
#734 - Add support for typeahead lookups on @AdminPresentationToOne fields
#734 - Fix NPEs relating to typeahead for Skus
#691 - Add logging switch for thread local instances that are not cleaned up
#691 - clean up thread local usage
#691 - Add logging switch for thread local instances that are not cleaned up
fds
#734 - Make typeahead lookups opt-in rather than opt-out
Fixes #736 - Fix an issue where filtering by a date and then sorting caused an exception
The real cause here is that when the criteria inputs were updated with the URL parameters, we were just parsing out the parameters into a JSON object (via BLCAdmin.history.getUrlParameters()) but forgetting that the parameter values themselves could be URI-encoded. This led itself to dates only, because date filter values have a space in them (yyyy.mm.dd HH:MM:SS). The criteria value was getting overwritten with yyyy.mm.dd%20HH:MM:SS and then when we attempted to sort that, the final value for the criteria ended up being yyyy.mm.dd%2520HH:MM:SS in order to encode the '%' sign.
Merge branch 'BroadleafCommerce-3.0.x' into BroadleafCommerce-3.1.x
Fixes #736 - Fix an issue where filtering by a date and then sorting caused an exception
The real cause here is that when the criteria inputs were updated with the URL parameters, we were just parsing out the parameters into a JSON object (via BLCAdmin.history.getUrlParameters()) but forgetting that the parameter values themselves could be URI-encoded. This led itself to dates only, because date filter values have a space in them (yyyy.mm.dd HH:MM:SS). The criteria value was getting overwritten with yyyy.mm.dd%20HH:MM:SS and then when we attempted to sort that, the final value for the criteria ended up being yyyy.mm.dd%2520HH:MM:SS in order to encode the '%' sign.

(cherry picked from commit e5ae7e812c8f66c30bd8a82b72cebc3339eabe28)
#737 - Category browsing with the DatabaseSearchService is broken
#424. Added logic to check the header first.  If the header isn't there,
it checks the isSecure() method of the request.  Otherwise, it commences
a redirect.
(cherry picked from commit e82f8af129ba07c598e2a0b2859971955f18d2cd)
#424. Removed duplicate logic to check if this processor supports the
config attribute.
(cherry picked from commit 350de8545cc5f6f55a68b0924d2bc1d933b6514c)