Clean up MozL10n API use in Cost Control #1057795

This is relating bug 1057795
We prefer to use DOM API whenever possible. In the future we will want to standardize mozL10n as a WebAPI and the more we rely on DOM API the better. We mainly use mozL10n.setAttributes/getAttributes because it hides the JSON.serialize/JSON.parse on l10n-args.