refactor: extract completion logic from pipe to implement it into rec…

[andrey-canon]

Description

This move the completion logic from the pipeline step to the receiver, this also adds some logs to monitor which actions is triggered the pearson task

Testing instructions

Before

After

Additional information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.

Checklist for Merge

• Tested in a remote environment
• Updated documentation
• Rebased master/main
• Squashed commits

[johanseto]

I made a logic suggestion. I think test would pass with that change.

[johanseto]

Suggested change

	if is_complete and not graded:
	LOGGER.info(
	"Initializing rti task for the user %s, action triggered by course completion status",
	instance.user_id,
	)
	if getattr(settings, "USE_PEARSON_ENGINE_SERVICE", False):
	real_time_import_task_v2.delay(
	user_id=instance.user_id,
	exam_id=str(instance.context_key),
	action_name="rti",
	)
	else:
	real_time_import_task.delay(
	user_id=instance.user_id,
	course_id=str(instance.context_key),
	)
	if (not is_complete) or graded:
	return
	LOGGER.info(
	"Initializing rti task for the user %s, action triggered by course completion status",
	instance.user_id,
	)
	if getattr(settings, "USE_PEARSON_ENGINE_SERVICE", False):
	real_time_import_task_v2.delay(
	user_id=instance.user_id,
	exam_id=str(instance.context_key),
	action_name="rti",
	)
	else:
	real_time_import_task.delay(
	user_id=instance.user_id,
	course_id=str(instance.context_key),
	)

[andrey-canon]

very similar to my first approach if graded or not is_complete: but I decided to leave as similar as possible in order to make easier the review, anyway I will update that