Changed how BuildMaster release number is matched to TFS work items for issues list

Previously, the whole iteration path had to match the BuildMaster release number; now, if the release number appears anywhere in the iteration path for that work item, it will be included in the issues list for that release. The normal rules for filtering on area path and project still apply, so if the area path doesn't match, the work item will never be included regardless of what the iteration path is. This is useful for people who have nested TFS iteration paths with the release at an arbitrary level in the hierarchy, e.g. Project\Area1\1.0.0\Iteration 2.