Need help - Not able to set up development provisioning profiles (ios) with development build

### Build/Submit details page URL

_No response_

### Summary

I am developing with "family control (development)" capability. All my bundle ids have enabled family control (development) capability, however, when I am running
```
eas build -p ios --profile development
```
I see the logs and it is trying to set up ad-hoc profile, and eventually I get following errors saying the provisioning profile does not support Family Control (development) capability. (See log)

This is my first official ios project, so I had to ask claude a lot, not sure if I am doing it right but I do see there are 4 tabs under build credentials of the eas project and it is always ad hoc. From what claude says, I need to use development credential / profile to make use of the family control (development) capability. I checked the apple develop console and I also see the provisioning profiles EAS created have type "Ad hoc" rather than development. Wondering is this a corner case that EAS does not support?

### Managed or bare?

Managed

### Environment

```
expo-env-info 2.0.7 environment info:
System:
OS: macOS 15.6.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm
Managers:
CocoaPods: 1.16.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.5, iOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5
IDEs:
Xcode: 16.4/16F6 - /usr/bin/xcodebuild
npmPackages:
expo: 53.0.22 => 53.0.22
expo-router: ~5.1.6 => 5.1.6
react: 19.0.0 => 19.0.0
react-native: ^0.79.0 => 0.79.0
npmGlobalPackages:
eas-cli: 16.19.3
Expo Workflow: bare
```

```
npx expo-doctor
Need to install the following packages:
expo-doctor@1.17.8
Ok to proceed? (y) y

14/17 checks passed. 3 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

✖ Check Expo config (app.json/ app.config.js) schema
Error validating fields in /Users/jasperwu/reactApp/bittersweet/bittersweet-mobile/app.json:
Field: ios - should NOT have additional property 'deploymentTarget'.
Advice:
Resolve schema errors in your app config. Learn more.

✖ Validate packages against React Native Directory package metadata
The following issues were found when validating your dependencies against React Native Directory:
Untested on New Architecture: immer
No metadata available: react-native-device-activity
Advice:
Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

✖ Check that packages match versions required by installed Expo SDK
The following packages should be updated for best compatibility with the installed expo version:
react-native@0.79.0 - expected version: 0.79.5
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies
Advice:
Use 'npx expo install --check' to review and upgrade your dependencies.
To ignore specific packages, add them to "expo.install.exclude" in package.json. Learn more.

3 checks failed, indicating possible issues with the project.
```

### Error output

✖ Build failed
🍏 iOS build failed:
- Provisioning profile "*[expo] com.path2us.bittersweet.ShieldAction AdHoc 1758257441180" doesn't include the com.apple.developer.family-controls entitlement and doesn't match the entitlements file's value for the com.apple.security.application-groups entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. (in target 'ShieldAction' from project 'bittersweetmobile')
- Provisioning profile "*[expo] com.path2us.bittersweet AdHoc 1758257421014" doesn't support the Family Controls (Development) capability. (in target 'bittersweetmobile' from project 'bittersweetmobile')
- Provisioning profile "*[expo] com.path2us.bittersweet AdHoc 1758257421014" doesn't include the com.apple.developer.family-controls entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. (in target 'bittersweetmobile' from project 'bittersweetmobile')
- Provisioning profile "*[expo] com.path2us.bittersweet.ActivityMonitorExtension AdHoc 1758257445353" doesn't support the Family Controls (Development) capability. (in target 'ActivityMonitorExtension' from project 'bittersweetmobile')
- Provisioning profile "*[expo] com.path2us.bittersweet.ActivityMonitorExtension AdHoc 1758257445353" doesn't include the com.apple.developer.family-controls entitlement and doesn't match the entitlements file's value for the com.apple.security.application-groups entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. (in target 'ActivityMonitorExtension' from project 'bittersweetmobile')
Refer to "Xcode Logs" below for additional, more detailed logs.

### Reproducible demo or steps to reproduce from a blank project

I can provide the following eas.json
```
{
"cli": {
"version": ">= 16.19.3",
"appVersionSource": "remote"
},
"build": {
"development": {
"distribution": "internal",
"developmentClient": true,
"ios": {
"buildConfiguration": "Debug",
"simulator": false
}
},
"preview": {
"distribution": "internal"
},
"production": {
"autoIncrement": true
}
},
"submit": {
"production": {}
}
}

```