Drop ia32 Windows target

[Half-Shot]

Fixes #1666

Discussed with product team beforehand as something we should just do at this point.

Checklist

• Ensure your code works with manual testing.
• New or updated public/exported symbols have accurate TSDoc documentation.
• Linter and other CI checks pass.
• Sign-off given on the changes (see CONTRIBUTING.md).

[t3chguy]

We need to communicate this to existing users. Either by creating a message in the affected users app or via deprecating publicly and setting a death date or both.

[Half-Shot]

We need to communicate this to existing users. Either by creating a message in the affected users app or via deprecating publicly and setting a death date or both.

I think we could add a toast (or banner?) for users on ia32 that tells them that they will be unsupported by X date. I do think the affected user pool will be very low, but I suppose in the range of 0.01~0.1% of users.

Actually thinking a bit more abstract here, can we just have a toast for unsupported operating systems. I can imagine that this is relatively common for MacOS / Linux as we deprecated every so often?

[langleyd]

@t3chguy Can the toast we have for unsupported browsers be easily built upon for unsupported OSes?

[t3chguy]

Perhaps but then you'd risk impacting a community maintained package for ia32, this would need to be a warning only for users of our own package surely

[langleyd]

@Half-Shot Is updating adding the upsupported OS toast(similar to the unupported browser one) something you would be able to take a look at as a part of this?

[Half-Shot]

@Half-Shot Is updating adding the upsupported OS toast(similar to the unupported browser one) something you would be able to take a look at as a part of this?

Pragmatically, I don't think I've got enough time on my hands to work on that. I do think it would be useful for now and in the future, but presently I'm overbooked.