feat(core): ensure KEL, ACDC, contact timestamps are used instead of record creation time

[Sotatek-TungNguyen2a]

Description

In many places where we create records we are letting the createdAt timestamp be Date.now() but it should match the KERIA times.

Checklist before requesting a review

Issue ticket number and link

• This PR has a valid ticket number or issue: (https://cardanofoundation.atlassian.net/browse/DTIS-1417)

Testing & Validation

• This PR has been tested/validated in IOS, Android and browser.
• The code has been tested locally with test coverage match expectations.
• Added new Unit/Component testing (if relevant).

Security

• No secrets are being committed (i.e. credentials, PII)
• This PR does not have any significant security implications

Code Review

• There is no unused functionality or blocks of commented out code (otherwise, please explain below)
• In addition to this PR, all relevant documentation (e.g. Confluence) and architecture diagrams (e.g. Miro) were updated

[jimcase]

In the UI CreareIdentifier.tsx, we have the method handleCreateIdentifier that is creating the Identify record like this:

const newIdentifier: IdentifierShortDetails = {
        id: identifier,
        displayName: identifierData.displayName,
        createdAtUTC: new Date().toISOString(),
        theme: selectedTheme,
        isPending: isPending,
      };

Should we set the createdAtUTC time to the one provided by keripy instead of new Date()? @iFergal

const identifierDetail = await this.props.signifyClient.identifiers().get(identifier);
new Date(identifierDetail.state.dt)

[iFergal]

@jimcase The state could be the datetime of a newer rotation event. But yes, this is what myself and Patrick mentioned this morning. I opened a PR just now on KERIA: WebOfTrust/keria#335

[iFergal]

Need to wait until next dev release of KERIA for latest change to get the real inception datetime.

[iFergal]

@jimcase I also misread your comment. Yes, except Bao's current PR is changing it so that it's created via callbacks so we can consolidate the two PRs. @Sotatek-BaoHoanga and @Sotatek-TungNguyen2a please coordinate here