Updated BuildConfig and Shipwright Build lists shows runs from another namespace

Description of problem:
When the user selects All namespaces in the admin perspective and navigates to Builds > BuildConfigs or Builds > Shipwright Builds (if the operator is installed) the last runs was selected based on their name. But the filter doesn't check that the Build / BuildRun are in the same namespace as the BuildConfig / Build.

Version-Release number of selected component (if applicable):
4.14 after we've merged ODC-7306 / https://github.com/openshift/console/pull/12809

How reproducible:
Always

Steps to Reproduce:

1. Create two namespaces
2. Create a BuildConfig with the same name in both namespaces
3. Start a Build for each BuildConfig
4. Navigate to Build > BuildConfigs and select "All namespaces"

For Shipwright Builds and BuildRun you need to install the Pipelines operator, the Shipwright operator, create a Shipwright Build Resource (to enable the SW operator) as well as to Builds and BuildsRuns in two different namespaces.

You can find some Shipwright Build samples here: https://github.com/openshift/console/tree/master/frontend/packages/shipwright-plugin/samples

Actual results:
Both BuildConfigs are shown, but both shows the same Build as last run.

Expected results:
Both BuildConfigs should show and link the Build from their own namespace.

Additional info:
This issue exists also in Pipelines, but we track this in another bug to backport that issue.