Fix some attributes and state for KC export

[rhysyngsun]

What are the relevant tickets?

N/A

What's this PR do?

• Switches createdTimestamp to an integer in milliseconds. The previous stringified value was being parse typically as some datetime in January of 1970. No clear reason why, no documentation as to what it should be aside from a long. API didn't seem to reject the value though, although arbitrary string values did get rejected. Timestamps in seconds had the same result.
• Added a --verbose flag that logs the requests, error responses are still always logged
• Added handling for skipped users, with a new action field on the model to reflect whether a user was actually exported or skipped because they already exist. Without this users who already existed were attempted to export perpetually.

How should this be manually tested?

Run ./manage.py migrate_users_to_keycloak --client-id admin-cli --client-secret SECRET --verbose and you should see verbose output.

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: keycloak_user_export/management/commands/migrate_users_to_keycloak.py

Function	Unhandled Issue
handle	JSONDecodeError: Expecting value: line 1 column 1 (char 0) keycloak_user_export.management.commands.migrate_users_to_keycloak in _re... Event Count: 1

---

_{Did you find this useful? React with a 👍 or 👎}