Code Quality: Migrate LayoutPreferences and FileTags keys to SHA256 hash

[seer-by-sentry]

Resolved / Related Issues

To prevent extra work, all changes to the Files codebase must link to an approved issue marked as Ready to build. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.

• Closes FILES-APP-37R

Steps used to test these changes

Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.

1. The issue was that: Registry key creation fails because LayoutPreferencesDatabase.FindPreferences uses excessively long file paths directly as registry key components, exceeding the 255-character limit.
2. Introduces a SHA256 hashing mechanism for file paths used as keys in LayoutPreferences and FileTags registries.
3. Implements a migration process to convert existing file path keys to their SHA256 hash equivalents.
4. Adds a migration marker to prevent repeated migrations.
5. Adds a helper function to check if a string is a hex string.

This fix was generated by Seer in Sentry, triggered by Yair. 👁️ Run ID: 600244

Not quite right? Click here to continue debugging with Seer.

[Copilot]

Pull Request Overview

This PR migrates LayoutPreferences and FileTags registry keys to use SHA256 hashes instead of full file paths to prevent registry key creation failures when file paths exceed the 255-character limit.

• Introduces SHA256 hashing for file paths used as registry keys
• Implements migration logic to convert existing file path keys to hashed equivalents
• Adds helper functions for hex string validation and SHA256 generation

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
ChecksumHelpers.cs	Adds new SHA256 hash generation method for file paths
FileTagsDatabase.cs	Replaces direct file path usage with SHA256 hashes and adds migration logic
LayoutPreferencesDatabase.cs	Replaces direct file path usage with SHA256 hashes and adds migration logic

Comments suppressed due to low confidence (2)

src/Files.App/Utils/FileTags/FileTagsDatabase.cs:318

• Missing parentheses around the logical OR operations. The condition should be: (c >= '0' && c <= '9') || (c >= 'a' && c <= 'f') || (c >= 'A' && c <= 'F') to ensure correct operator precedence.

			return value.All(c => c >= '0' && c <= '9' || c >= 'a' && c <= 'f' || c >= 'A' && c <= 'F');

src/Files.App/Helpers/Layout/LayoutPreferencesDatabase.cs:240

• Missing parentheses around the logical OR operations. The condition should be: (c >= '0' && c <= '9') || (c >= 'a' && c <= 'f') || (c >= 'A' && c <= 'F') to ensure correct operator precedence.

			return value.All(c => c >= '0' && c <= '9' || c >= 'a' && c <= 'f' || c >= 'A' && c <= 'F');

[Copilot]

The IsHexString method is duplicated in both FileTagsDatabase and LayoutPreferencesDatabase. Consider moving this utility method to a shared location like ChecksumHelpers to avoid code duplication.

Suggested change

	private static bool IsHexString(string value)
	{
	return value.All(c => c >= '0' && c <= '9' || c >= 'a' && c <= 'f' || c >= 'A' && c <= 'F');
	}
	// Removed IsHexString method. Use ChecksumHelpers.IsHexString instead.