Remove Fingerprint Generation Capabilities

[decaffeinatedio]

This PR removes the most problematic fingerprint generation from synthetic.rs while keeping the overall workflow intact (and tests still passing).

Even in a prototype, I would strongly recommend against creating a fingerprint like this.

Why?

• In its default form, it cannot be effectively controlled or observed by an end user. In its default form, an incognito session and a standard browser session could be linked together by any platforms downstream. Does that meet user expectations?
• Running this out of the box is likely unlawful in many regions of the world. Shipping this without a big warning label on the side (much less implementing some simple consent checks) sends a poor message about what smart defaults look like in 2025.
• While I don't expect activists and browser makers to be enthused about this project (or much adtech does at all), the signal of integrating a super cookie fingerprint as a v.0 priority is a great way to reinforce the existing convictions of that group and spur more drastic actions.

[iabshailley]

We will not take any action on this PR at this time. The project will be governed by the Trusted Server task force that is being constituted and it will make decisions on features and functions of the trusted server. The current code base is a proof of concept to demonstrate certain capabilities.

[sulleh]

Wasn't the request for us to specifically submit a PR with changes we'd recommend or like to see?