👔 Reset the cached pipeline state in the profile as well

[shankari]

Before this change, the pipeline reset script would change the get_pipeline_state_db() but not the cached pipeline start and end in the profile.

Since we now use the profile to decide whether to run the pipeline, this led to issues where the pipeline for a user would not re-run even after the pipeline was reset.
e-mission/e-mission-docs#1105 (comment)

I wonder if we should use only the pipeline state to decide whether or not to run the pipeline, instead of the profile. It seems like restructuring to use a single source of truth would be good.

Testing done:
Ran it to reset our test user back to 2024-07-30; verified that the value in the profile was reset
Verified that the pipeline was not skipped on the run after the reset

[shankari]

@JGreenlee for visibility
@TeachMeTW can you please add the tests for this functionality?

Copilot suggests something like

class TestResetPipeline(unittest.TestCase):
    @patch("emission.pipeline.reset.edb.get_analysis_timeseries_db")
    @patch("emission.pipeline.reset.edb.get_pipeline_state_db")
    @patch("emission.pipeline.reset.edb.get_profile_db")
    def test_reset_user_to_start(self, mock_get_profile_db, mock_get_pipeline_state_db, mock_get_analysis_timeseries_db):
        # Mock the database methods
        mock_analysis_db = MagicMock()
        mock_pipeline_db = MagicMock()
        mock_profile_db = MagicMock()

        mock_get_analysis_timeseries_db.return_value = mock_analysis_db
        mock_get_pipeline_state_db.return_value = mock_pipeline_db
        mock_get_profile_db.return_value = mock_profile_db

        # Mock the count_documents and delete_many methods
        mock_analysis_db.count_documents.return_value = 10
        mock_pipeline_db.count_documents.return_value = 5
        mock_analysis_db.delete_many.return_value.raw_result = {"n": 10}
        mock_pipeline_db.delete_many.return_value.raw_result = {"n": 5}
        mock_profile_db.update_one.return_value.raw_result = {"nModified": 1}

        # Call the function
        reset.reset_user_to_start("test_user_id", is_dry_run=False)

        # Assertions
        mock_analysis_db.count_documents.assert_called_once_with({"user_id": "test_user_id"})
        mock_pipeline_db.count_documents.assert_called_once_with({"user_id": "test_user_id"})
        mock_analysis_db.delete_many.assert_called_once_with({"user_id": "test_user_id"})
        mock_pipeline_db.delete_many.assert_called_once_with({"user_id": "test_user_id"})
        mock_profile_db.update_one.assert_called_once_with(
            {"user_id": "test_user_id"},
            {"$set": {"pipeline_range.start_ts": None, "pipeline_range.end_ts": None}}
        )

Please make sure to use your best judgement in integrating it with the rest of the codebase; find the current test suite for pipeline resets; make sure that the checks are actually checking the new functionality here, etc.

[TeachMeTW]

Added test in #1068
I'll fix the commits once 1067 is merged
I know copilot advised mocking but I believe using intake pipeline and real examples was more intuitive and easier to grasp

[shankari]

Also made some additional logging changes to clean up this branch before I am done