move GPC preferences before we send fidesInitialized event

[eastandwestwind]

Closes #3489

Code Changes

• move GPC preferences before we send fidesInitialized event

Steps to Confirm

• Enable an opt-out notice (opt-in by default)
• Enable GPC signal
• Load a site with fides.js installed
• Observe the console events and see that the initial FidesInitialized event should have the opt-out notice set to false

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation:
  • documentation complete, PR opened in fidesdocs
  • documentation issue created in fidesdocs
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md
• For API changes, the Postman collection has been updated

Description Of Changes

Write some things here about the changes and any potential caveats

[cypress]

Passing run #2907 ↗︎

0	4	0	0	0
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.

Details:

Merge dfe36dc into a081a87...
Project: fides	Commit: ac1f42d4ef ℹ️
Status: Passed	Duration: 00:58 💡
Started: Jun 26, 2023 3:23 PM	Ended: Jun 26, 2023 3:24 PM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[allisonking]

woot this worked great, nice job!

[allisonking]

Actually one thing I just thought of: this means a FidesUpdated could potentially be sent before a FidesInitialized, since the GPC func sends a FidesUpdated. is that okay?

[eastandwestwind]

@allisonking regarding your Q:

Actually one thing I just thought of: this means a FidesUpdated could potentially be sent before a FidesInitialized, since the GPC func sends a FidesUpdated. is that okay?

This scenario may happen if there is no existing Fides cookie. Because we will always send the FidesInitialized event after the FidesUpdated event, it's OK since a subscriber to events would receive the initialized event.