Fields with numeric consts default value are incorrectly marked as required

Controller

	public function createRoomV2(
		string $name,
		int $type = Room::TYPE_GROUP,
		int $readOnly = Room::READ_WRITE,
		int $listable = Room::LISTABLE_NONE,
		int $messageExpiration = 0,
		int $lobbyState = Webinary::LOBBY_NONE,
		?int $lobbyTimer = null,
		int $sipEnabled = Webinary::SIP_DISABLED,
		int $permissions = Attendee::PERMISSIONS_DEFAULT,
		int $recordingConsent = RecordingService::CONSENT_REQUIRED_NO,
		int $mentionPermissions = Room::MENTION_PERMISSIONS_EVERYONE,
		string $description = '',
		?string $password = null,
		?string $objectType = null,
		?string $objectId = null,
		?string $emoji = null,
		?string $avatarColor = null,
		array $participants = [],
	): DataResponse {

Expectation

Only name is marked as required

Actual

Also fields with consts as default are marked as required

Start by tracing how the extractor interprets the createRoomV2 controller parameters and determines whether each parameter is required. Verify the handling of numeric constant defaults against literal defaults, and consider the work done when only name remains required for the shown signature.