specs for Birth Cohort and eligibility #3324
Birth Cohort and eligibility #3324
removed part one from NCS hi-lo.xml #3325
Confirming specimens no longer creates duplicate records. #3395
Re-add call to mark_activity_occurred

Commit 2a537ce8a1ad4d0bf0b8e841478dfc0980927aae
added an mark_activity_occurred call from update.

The very next commit for this file
0fecc6c310b06ba188f4055a1a4458baf2887f67
removed this call.

This commit re-adds it. We need this call after update
because users can get stuck when performing activities
for an event at the informed consent activity for a participant
with an existing consent.

Changes in #3170 and specifically the task #3194 should
address the issue.
Merge branch 'master' of https://github.com/NUBIC/ncs_navigator_core
Updated specs to use custom_recruitment_strategy

Both these specs used a method 'set_recruitment_strategy'
which set the NcsNavigatorCore.recruitment_strategy.
While fine when running the specs individually this caused
several errors in the CI build.

When updating application level configuration variables in tests
we should take care to revert that value back to the original value
after the test needing the change has run.
Merge pull request #40 from NUBIC/task_3325_move_from_birth_cohort_segment_to_birth_segment

Birth Cohort and Eligibility #3325
Merge pull request #42 from NUBIC/issue_3395

Confirming specimens adds a duplicating record on the tab.
Needed for 1.3.9.pre testing.
Filter consents by event date range. #3263.

N.b.: I'm not sure if the use of Date::Infinity here is kosher. It
works and all, but I can't tell if it is intended to be part of the
public API. It is listed in rubyspec, but only with stubs. And, as
noted in the code, it works as the end of a range but not the start
(since it doesn't implement #succ).

Anyway, future developers feel free to curse my memory when it gets
removed it in Ruby 3.14.
Shift lo-hi determination to informed consent events. Closes #3263.

This commit changes the import-time lo-hi determination decision in
two ways. First, It moves it out of OperationalImporter and into
`Participant#set_state_for_event_type` along with all the other state
detail decisions. Second, it associates the decision with each
Informed Consent event, instead of the Low-High Conversion event. (It
turns out that the Low-High conversion event is not consistently
recorded across SCs.)

This required a fair number of changes to the importer specs. Some are
expected and obvious reflections of the new behavior. Others are
because the new model resulted in the test participant's odd sequence
of events triggering a (pre-existing) implicit conversion to hi on
PV1.