Description:
------------
When using PharData::buildFromIterator() to create a Tar archive file permissions are not kept.

Same bug as #77022 but its triggered by using buildFromIterator. Making a new report  rather than comment on #77022 because #77022 was marked as "SEC BUG".

Even adding the same file with iterator and with addFile($file, 'new-name') will result in a tar archive with two files with different permissions.

Test script:
---------------
https://3v4l.org/qCPRH

<?php
var_dump(decoct(umask(22)));
$srcDir = '/tmp/files';
mkdir($srcDir);
foreach([1, 2] as $i){
	$file = tempnam($srcDir, 'test');
	printf("File$i - %o\n", stat($file)['mode']);
}
$phar = new \PharData('/tmp/test.tar', null, null, \Phar::TAR);
$phar->buildFromIterator(new \RecursiveDirectoryIterator($srcDir, \FilesystemIterator::SKIP_DOTS), $srcDir);

$phar->addFile($file, 'added-with-add-file');
$phar->extractTo('/tmp/pharFiles');

foreach(new \RecursiveDirectoryIterator('/tmp/pharFiles', \FilesystemIterator::SKIP_DOTS) as $iFile) {
	printf('From ' . ($iFile->getFilename() === 'added-with-add-file' ? 'addFile':'Iterator'). " - %o\n", $iFile->getPerms());
}


Expected result:
----------------
Files added to tar using PharData::buildFromIterator should keep the original permissions or respect the umask, same as files added by using PharData::addFile.

From addFile - 100600
From Iterator - 100600


Actual result:
--------------
Files added from iterator don't keep correct permissions

From addFile - 100600
From Iterator - 100666

Before #77022 was fixed
From addFile - 100666
From Iterator - 100666