use correct values for subscriptionKey and endpointKey for qna services

[a-b-r-o-w-n]

closes #1286
closes #1287
closes #1289

Fixed

• [main] use correct values for subscriptionKey and endpointKey for qna services, in PR #1301
• [client] fix link to manage qna service, in PR #1301

[coveralls]

Pull Request Test Coverage Report for Build 2011

• 14 of 14 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.01%) to 50.41%

---

Totals
Change from base Build 2002:	0.01%
Covered Lines:	4512
Relevant Lines:	8354

---

💛 - Coveralls

[justinwilaby]

@a-b-r-o-w-n - You might be able to cover the continuation in the loop thusly:

let success = 100
const mockArgsPassedToFetch = [];
let mockResponses;
jest.mock('node-fetch', () => {
  const fetch = (url, headers) => {
    mockArgsPassedToFetch.push({ url, headers });
    return {
      ok: (--success > 0),
      json: async () => mockResponses.shift(),
      text: async () => mockResponses.shift(),
    };
  };
  (fetch as any).Headers = class {};
  (fetch as any).Response = class {};
  return fetch;
});

...
it('should skip over responses that do not succeed', () => {
  success = 1;
 // do stuff
 expect(result.services.length).toBe(1);
});

[a-b-r-o-w-n]

@justinwilaby That's a good idea. I have another implementation that I just wrapped up. I'll push it once I see that there is coverage for that line.

[tonyanziano]

👍