Img conflict name

[aarbi]

fixes #3156

[aarbi]

the hashes are different from what I got in my local machine.
I haven't found a method in the File class that supports fuzzy search.

I will start by getting the hashes of files generated on the Github actions environement and stick them in the tests.
if this is not good enough, I will add a helped function that uses fs-extra to do something like this:

/**
 * Finds the files in a folder that have a given file name and extension.
 * This helps when looking for files generated by webpack with hashes
 *
 * @param {string} path
 * @param {string} fileName
 * @param {string} extension
 * @returns
 */
export async function filesFoundInFolder(path, fileName, extension) {
	const filesInFolder = await fs.readdir(path);
	const filteredFiles = filesInFolder.filter(
		f => f.startsWith(fileName) && f.endsWith(extension)
	);

	return filteredFiles;
}

Then within the test, we can check the length of the returned array like so:

t.true(File.exists(`test/fixtures/app/dist/images/img.66162.svg`));
becomes:
t.true( (await filesFoundInFolder('test/fixtures/app/dist/images/', 'img', 'svg')).length == 1 );

[aarbi]

So webpack hashes aren't generated based on the absolute paths, but from the where the root dir of the project. Which means that the hashes are consistent if the test are run in local and github actions. I set the exact has I had in local and it works now in Github. It didn't work earlier to me because I used 6 chars instead of 8