Previously it would fail, now event detection will work, albeit with
some errors due to #834.

Fixes #798

Update time toString() methods

Closes #637, #590, #591, and #825

See merge request !188

Fix conflit in TimeSpanDragForceTest

Remove step size limits in analytic propagators

Closes #830

See merge request !192

Align attitude with propagation frame

Closes #586

See merge request !189

Merge changes.xml

Finalized fix for #797

See merge request !193

Sum additions to OrekitMessages

Keep all tests added to CloseEventsAbstractTest,
FieldCloseEventsAbstractTest.

Remove unused imports, fix bug in test where wrong value was used in
assertion.

Also remove Propagator.DEFAULT_LAW. Use IntertialProvider.of(Frame)
instead. See discussion on !189. Part of #586.

Anne-Laure did most of the work to add more informative messages when
root finding for event detection fails. This commit adds a few polishes.
- Added Anne-Laure Lugan as a contributor
- Updated messages to print g values to full precision.
- Made try {} as small as possible since catch() is so broad
- Fix checkstyle warnings
- Add test to check message is formatted correctly

Issue 797 : Improve investigation while encoutering a MathIllegalStateException

See merge request !165

Fix #685 analytic propagator null reset state

Closes #685

See merge request !191

Fix #618 ClasspathCrawler match file name only

Closes #618

See merge request !190

And also the related FieldPropagator.DEFAULT_LAW and
IntertialProvider.EME2000_ALIGNED. Left a couple usages in the tests
that were necesscessary for proper class loading and for testing the
deprecated values. #586

Previously when an analytic propagator handled a continue event the
first part of the step would be passed to the OrekitStepHandler twice.
Now it is only passed once. Seems to have been present when
AbstractAnalyticalPropagator was created, about a decade ago, and not
detected in all the changes since then, so I guess no one uses that
combination much.

Change FieldAbstractAnalyticalPropagator to use the same logic as
AbstractAnalyticalPropagator in accept step to decide if it is the last
step.

Previously when there was a step handler analytic propagators were
forced to take small steps though EventDetector and OrekitStepHandler
can both use large steps. Removed this unnecessary restriction to
improve performance.

Fix #830

These methods are incorrect. They should use the default implementation
instead.

Previously a null reset state behaved as CONTINUE with analytic
propagators but not with integrated propagators. This was an
undocumented "feature". Removed it to be consistent.

Previously ClasspathCrawler matched the whole path against supported
names which caused problems with ^ as other loaders only matched the
file name. Added a test case.

Implemented for all analytic and the GlONASS propagator. The DSST and
Numerical propagator do not have a frame available in their constructor,
so the new behavior could not be implemented. Aligning the attitude
frame with the propagation frame speeds up propagation when the user
does not care about attitude and it many cases it removes a dependence
on the default data context.

Fix #586

It now has better performance when the attitude is aligned with the
propagation reference frame by avoiding multiplying by zero. With
analytic propagators using this attitude provider instead of the default
has been observed to result in a speed up of 2 in some cases, e.g. with
the TLEPropagator.

For #586

Update it to be the same as AbsoluteDate.toString() by calling that
method. Converting to a string does not include any field information.

Part of #825