pipelines_config API returns a Repository Not found error if Pipelines is not enabled

Issue Summary

If we run a GET call to pipelines_config endpoint, the API returns a Repository Not found error if Pipelines has never been enabled for that repository.

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Run a GET call on the pipelines_config endpoint to a repository that has never had Pipelines enabled:

   curl -X GET -u "username":"apppassword" -H "Content-Type: application/json" https://api.bitbucket.org/2.0/repositories/workspaceID/reposlug/pipelines_config
   

Expected Results

Indication that Pipelines is disabled.

Actual Results

{
"error": {
"message": "Not found",
"detail": "Repository
{xxxxxx} does not exist for account {xxxxxx}

.",
"data": {
"key": "account-service.repository.not-found",
"arguments": {
"uuid": "
{xxxxxx}
"
}
}
}
}

So the output is indicating that the repository is not present, NOT that Pipelines is disabled.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available