[exupdates][ios] Run swiftlint --fix (#21664)

# Why

To appease the swiftlint gods.

# Test Plan

Build.

# Checklist

<!--
Please check the appropriate items below if they apply to your

[exupdates][ios] Run swiftlint --fix (#21664)

# Why

To appease the swiftlint gods.

# Test Plan

Build.

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[exupdates][ios] rename swift classes to be more swifty (#21620)

# Why

As requested by @douglowder. These classes can be better-named and then
just expose the `EXUpdates` prefix in objective-c t

[exupdates][ios] rename swift classes to be more swifty (#21620)

# Why

As requested by @douglowder. These classes can be better-named and then
just expose the `EXUpdates` prefix in objective-c type names.

# How

Rename. Going to land this very soon to avoid bad merge conflicts. I'm
expected swiftlint will fail on this and will eat up all our API quota
as well.

# Test Plan

Build and run expo go, run all tests.

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...