[M] DUP - change/update pass number incrementor

[JLWade]

We have recently discovered some limitations to the way reservation numbers or pass numbers are being incremented and need to resolve this prior to it causing a conflict (ie. two passes with the same number).

Acceptance Criteria:

Given I'm a park visitor When I book a day use pass Then I receive my pass with a unique reservation number that has not been used previously.

Development Checklist:

• [ ] Number generator should be converted to a hex based-string (use https://www.npmjs.com/package/crypto-js)

Workflows:

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

Dependencies

• Blocked by
• Blocking

[Dianadec]

Refinement Notes:

• pass is a random 8-10 digit number
• once there are 45k passes in a park, 10% chance the new pass may collide with an existing one
• what if: we added another 3 digits (or letters) onto the end so that we don't need to worry about it for a number of years?
• Still need to action this now.

[Dianadec]

@marklise will update the AC/dev checklist according to refinement discussion notes.