[FEATURE] Provide an option to force reprocessing during update #323

[prithvi-moonshot]

Implements new cli flag --full-reprocess in order to invalidate cache during reexport.

closes #323

[georgeh0]

These lock file changes are unexpected. We're using yarn, so by default use yarnpkg.com instead of npmjs.org. Please revert change of this file.

[georgeh0]

What FullReprocess achieves is roughly a superset of ReexportTargets, so for things that need to happen on ReexportTargets mode, they need to happen for FullReprocess too

https://github.com/search?q=repo%3Acocoindex-io%2Fcocoindex%20ReexportTargets&type=code

I think we can consider add a method UpdateMode::needs_full_export() (which returns true on both modes) and use this one in many places above.

[prithvi-moonshot]

Just added this in the latest commit. Let me know what you think!

[prithvi-moonshot]

@georgeh0 so I was having problems pushing this commit due to a reason unrelated to this particular issue. I did a git pull a short while ago and one of new changes it brought was this example called image-search that has a type error. In order to push this commit to my remote branch I added a # type: ignore[misc] as that was the error code the type check was showing. Now a different type error is causing the GitHub pipeline test to fail. How should I proceed as this is an unrelated issue?

[prithvi-moonshot]

@georgeh0 Hey, so I decided to fix the commit issue by just expanding the scope of # type: ignore as I have seen it being used in other examples too. This commit is ready for review