[Job graph] Include respository from pipeline selector in filtering (#29191)

## Summary & Motivation
as titled

## How I Tested These Changes

Logged into an organization where job names are not unique across
deployments and saw that we correctly filtered assets to the right job
by including the repository location and name.

Author: salazarm

Diff for: js_modules/dagster-ui/packages/ui-core/src/asset-graph/useAssetGraphData.tsx

@@ -156,7 +156,13 @@ export function useAssetGraphData(opsQuery: string, options: AssetGraphFetchScop
   const repoFilteredNodes = useMemo(() => {
     let matching = allNodes;
     if (pipelineSelector) {
-      matching = matching.filter((node) => node.jobNames.includes(pipelineSelector.pipelineName));
+      matching = matching.filter((node) => {
+        return (
+          node.jobNames.includes(pipelineSelector.pipelineName) &&
+          node.repository.name === pipelineSelector.repositoryName &&
+          node.repository.location.name === pipelineSelector.repositoryLocationName
+        );
+      });
     }
     if (groupSelector) {
       matching = matching.filter((node) => {