feat(cypress): differentiate browser/node in exports

[delatrie]

Context

The PR adds the node and browser conditions into allure-cypress's exports section, which allows importing "allure-cypress" in both the browser and the Node sides:

import "allure-cypress"; // the browser side code in support/e2e.js
import { allureCypress } from "allure-cypress"; // in cypress.config.js
import { allureCypress } from "allure-cypress/reporter"; // the same as above; backward compatibility

Additionally, users who mistakenly import "allure-cypress/reporter" in the browser-side code will get a more clear Could not resolve "allure-cypress/reporter" error instead of failing somewhere deep inside of "allure-js-commons" code with some failed Node-related import like "node:fs".