feat: make report Google Analytics configurable

[grootstebozewolf]

Summary

• Add isAnalyticsEnabled() helper in @allurereport/plugin-api (Allure 2 ALLURE_NO_ANALYTICS parity).
• Promote analyticsEnable to core config (not per-plugin), resolve once in AllureReport, and pass via PluginContext to awesome, classic, dashboard, and allure2 generators so GA can be omitted from report HTML.

Fixes #476

Usage

// allurerc.mjs
export default {
  analyticsEnable: false,
  plugins: {
    awesome: {
      options: {},
    },
  },
};

Or environment (Allure 2 style):

export ALLURE_NO_ANALYTICS=true

Env opt-out wins over the core config option.

Test plan

• yarn workspace @allurereport/plugin-api test — analytics resolver cases
• yarn workspace @allurereport/core test — config resolve includes analyticsEnable
• yarn workspace @allurereport/plugin-allure2 test — generateStaticFiles embeds/omits gtag for default, option false, and env true
• yarn workspace @allurereport/plugin-awesome test — plugin context fixtures

[baev]

maybe we should promote analyticsEnabled knob to the core? I don't think we will need to have analytics enabled for one plugin and disabled for the other

[just-boris]

Hello team

It seems like the review comment has been addressed. is there anything else preventing release of this?

This missing flag is a blocker for some teams looking to upgrade to Allure v3

[baev]

BTW I would rename analyticsEnable -> analyticsDisable so the default/non provided value match the default behaviour