feat: use customer id when present whilst creating a premium order

[pavelbrm]

Summary

This PR makes it possible for the known customer to be passed when creating a premium order. Additionally, this makes use of the customer information obtained from the old session when recreating one (mainly as part of the set trial days call).

Type of Change

• Product feature
• Bug fix
• Performance improvement
• Refactor
• Other

Tested Environments

• Development
• Staging
• Production

Before Requesting Review

• Does your code build cleanly without any errors or warnings?
• Have you used auto closing keywords?
• Have you added tests for new functionality?
• Have validated query efficiency for new database queries?
• Have documented new functionality in README or in comments?
• Have you squashed all intermediate commits?
• Is there a clear title that explains what the PR does?
• Have you used intuitive function, variable and other naming?
• Have you requested security and/or privacy review if needed
• Have you performed a self review of this PR?

Manual Test Plan

[clD11]

LGTM approved.

[kdenhartog]

LGTM - reviewed this as a part of https://github.com/brave/reviews/issues/1822

As long as I'm understanding the flow of this properly, I think we are introducing a correlating tracker here that we don't want. I need to keep reviewing to be sure, but definitely want to call it out early so we can revert this here and find a different approach to this if it is the case.

[kdenhartog]

Thanks for adding these tests in here - it made it much simpler to understand what this change was doing.

[pavelbrm]

As long as I'm understanding the flow of this properly, I think we are introducing a correlating tracker here that we don't want.

I don't think so. This has always been here in a slightly different form. This data is not kept in SKUs. SKUs used to figure out the customer id itself in some flows, but now it accepts it.