PipelineName does not perform an exact search - results in errors if pipelines contain the same name

## Issue
Mutiple pipelines are returned when `releaseApi.getReleaseDefinitions` and `buildApi.getDefinitions` are called if the pipeline name supplied exists within the pipeline name.

i.e.
If you have two pipelines called: `myFirstPipeline` and `myFirstPipeline - Copy` and you run this action with a pipeline name of `myFirstPipeline` you will get an error:
```bash
> **Error**: More than 1 Pipeline named "myFirstPipeline" found in project "myproject"
```

### Expected Behavior
From the above example, running this action with a pipeline name of `myFirstPipeline` should execute the pipeline named `myFirstPipeline` and not error saying it found more than one build definition.