The physics engine does not properly handle collision detection in certain cases between "Continuous Dynamic" Rigidbodies and "Kinematic Continuous" Rigidbodies

To reproduce:

1. Download attached project "ContinuousDynamicRigidbodyVsKinematicContinuousRigidbodyCollisionBug.zip" and open in Unity
2. Open "TestScene" scene
Note: Observe Hierarchy - there is a "Capsule" gameObject with Rigidbody that is set to "Continuous Dynamic" Collision Detection. In "OscillationPivot" gameObject there is a "Box" gameObject with a Kinematic Rigidbody which is set to "Continuous" Collision Detection
3. Enter Play mode
Note: Observe that the "Capsule" gameObject get an impulse causing it to move towards the "Box" gameObject at a constant speed. The "Box" will begin oscillating back and forth according to a Sine Wave. Later, the "Capsule" appears to collide with the "Box" when they aren't actually touching and the "Capsule" appears to stop (despite having a non-zero velocity). Also, observe that there are rapid OnCollisionEnter/Exits being sent. As the "Box" oscillates back towards the "Capsule", observe that the "Capsule" phases through the "Box" and then get shot out through the side of the "Box"

Notes:
- This issue appears on Windows and OSX
- The capsule has "Continuous Dynamic" detection, non-kinematic and no gravity. It is moved with a single Rigidbody.velocity = ... in Awake
- The box has "Continuous" detection and is kinematic. Its position is set every FixedUpdate with a Rigidbody.MovePosition call
- This behavior only happens with specific scene setups (like the one on this project). It seems to depend on the speeds of the involved Rigidbodies and the size of their Colliders.
- Workaround: If you disable "Continuous" Collision Detection on the "Capsule" or if you set the "Box" to "Discrete" Collision Detection, the collision resolves as expected

Reproduced on Unity 2017.2.0b7, 2017.2.0p2, 2017.3.0b10 and 2018.1.0a5
Not reproduced on Unity 2017.1.1p2 and 2017.2.0b6
Regression on Unity 2017.2.0b7