AssestReserve's governed APIs are mis-configured

[Chris-Hibbert]

Describe the bug

While refactoring AssetReserve to remove AMM dependencies (#7055), I became suspicious of the way the reserve configures its governed APIs. After the removal the only governed API will be burnFeesToReduceShortfall.

I think there's a problem in contractHelper.js. makeFarGovernorFacet takes governedApis as a parameter, but makeGovernorFacet does not, which means it can't add getGovernedApis() or getGovernedApiNames() to the creatorFacet. In addition, AssetReserve doesn't include governedApis in its call to makeVirtualGovernorFacet. fluxAggregatorContract.js shows an example of how to do it.

To Reproduce

test-reserve verifies that burnFeesToReduceShortfall can be called, but it's using the puppetContractGovernor, which cheats. I verified it using test-gov-collateral, which configures a real AssetReserve. I inserted a debugger statement in contractGovernor.js to verify that in initApiGovernance getGovernedNames returns ["burnFeesToReduceShortfall"], but governedApis` is empty.

Expected behavior

governance should be able to invoke burnFeesToReduceShortfall

[Chris-Hibbert]

I don't know whether I was confused before, or whether this was repaired in a way I haven't found by looking through the file history, but there's nothing wrong here.
When I do the same thing that's described under To Reproduce, I can see that burnFeesToReduceShortfall is present both in governedApis and getGovernedNames.