Fix documentation examples of new UseCompatible* rules

[bergmeister]

PR Summary

• Enabled is not a valid key for the settings, therefore examples using settings file did not work
• Use profile string name that is available in the shipped version so that examples work better out of the box

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

[rjmholt]

Good catches

[rjmholt]

Note that these are valid profile names, but not ones we ship now

[bergmeister]

Ok, I thought I could just create my own profile and name the file foo and it would to file name based matching like the old UseCompatibleCmdlets rule?

[rjmholt]

If you put it in the profile directory, that should work, yes. There's a method that takes a profile and turns it into a path:

PSScriptAnalyzer/Rules/CompatibilityRules/CompatibilityRule.cs

Lines 174 to 206 in 4f8e34e

	private string NormalizeProfileNameToAbsolutePath(string profileName)
	{
	// Reject null or empty paths
	if (string.IsNullOrEmpty(profileName))
	{
	throw new ArgumentException($"{nameof(profileName)} cannot be null or empty");
	}
	// Accept absolute paths verbatim. There may be issues with paths like "/here" in Windows
	if (Path.IsPathRooted(profileName))
	{
	return profileName;
	}
	// Reject relative paths
	if (profileName.Contains("\\")
	|| profileName.Contains("/")
	|| profileName.Equals(".")
	|| profileName.Equals(".."))
	{
	throw new ArgumentException($"Compatibility profile specified as '{profileName}'. Compatibility profiles cannot be specified by relative path.");
	}
	// Profiles might be given by pure name, in which case tack ".json" onto the end
	string extension = Path.GetExtension(profileName);
	if (string.IsNullOrEmpty(extension) || s_falseProfileExtensionPattern.IsMatch(extension))
	{
	profileName = profileName + ".json";
	}
	// Names get looked for in the known profile directory
	return Path.Combine(_profileDir.FullName, profileName);
	}