feat: Add BulkImport APIs and cron

[anku255]

Summary of change

(A few sentences about this PR)

Related issues

• Bulk User Import into SuperTokens #912

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your
changes work. Bonus points for screenshots and videos!)

Documentation changes

(If relevant, please create a PR in our docs repo, or create a checklist here
highlighting the necessary changes)

Checklist for important updates

• Changelog has been updated
  • If there are any db schema changes, mention those changes clearly
• coreDriverInterfaceSupported.json file has been updated (if needed)
• pluginInterfaceSupported.json file has been updated (if needed)
• Changes to the version if needed
  • In build.gradle
• If added a new paid feature, edit the getPaidFeatureStats function in FeatureFlag.java file
• Had installed and ran the pre-commit hook
• If there are new dependencies that have been added in build.gradle, please make sure to add them
  in implementationDependencies.json.
• Update function getValidFields in io/supertokens/config/CoreConfig.java if new aliases were added for any core config (similar to the access_token_signing_key_update_interval config alias).
• Issue this PR against the latest non released version branch.
  • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the
    latest branch (git branch --all) whose X.Y is greater than the latest released tag.
  • If no such branch exists, then create one from the latest released branch.
• If added a foreign key constraint on app_id_to_user_id table, make sure to delete from this table when deleting the user as well if deleteUserIdMappingToo is false.

[rishabhpoddar]

in this case, just return status code 200 ok

[rishabhpoddar]

in the right JSON output format ofc

[anku255]

I think its better to return an error because calling this API with no ids is not a valid case.

[rishabhpoddar]

it makes it harder for people to call the API. Cause if they have a loop in which they are calling the API, they will be forced to check if the input is empty before calling the API (as opposed to being flexible enough to allow them to check it after and then exit the loop)

[anku255]

That makes sense. I have updated it.

[rishabhpoddar]

in the bulkimport user type, we also need to allow plain text password cause it will be used during lazy migration task

[anku255]

This is done.

[rishabhpoddar]

need to allow parallelism:

• Allow devs to configure the parallelism. Default is 1.
• The prop can be called BULK_MIGRATION_PARALLELISM. This is a SaaS protected prop and can be added to PROTECTED_CONFIGS in CoreConfig.java. It should have the @NotConflictingInApp annotation.
• You can make a pool of proxy storages here based on the value of this prop, and create those number of threads as well.

[rishabhpoddar]

what is an example of how this output looks like?

[anku255]

{
  "errors": [
    "Role role1 does not exist.",
    "Role role2 does not exist.",
    "Invalid tenantId: t1 for emailpassword recipe.",
    "Invalid tenantId: t1 for thirdparty recipe.",
    "Invalid tenantId: t1 for passwordless recipe."
  ]
}

[rishabhpoddar]

i dont think the input should have a user prop. Cause then its like:

{
   user: {...}
}

Instead. it should just have all the details in the root of the json input

[anku255]

Done

[rishabhpoddar]

StorageQueryException usually means something like the db is down or something. All errors that are due to semantic issues have a different type (like emailalreadyexistsexception). Please double check error types