Feat/add optional policies

[AngryDragonite]

Resolves #33

Changes proposed in this pull request:

First of all, I added migrations that create columns: optional (boolean) and additional_info (JSON) inside fof_terms_policies table. Table fof-terms-policy-user has been enriched with is_accepted (boolean) column.

Modifications inside extend.php:

• added styles to forum
• added controller that handles rejection of an (optional) policy,
• added relationship fofTermsPoliciesState that allows to check which policies were accepted,
• removed Registered event listener, its functionality is now being handled inside RegisterMiddleware.php.

Modifications inside Policy.php, UserPolicyData.php, PolicyStoreController.php, PolicyRepository.php, RegisterPolicyValidator.php:

• generally speaking, added functionality that would integrate backend with new columns introduced in migrations,
• validator now forces users to accept only non-optional policies.

Modifications inside RegisterMiddleware.php:

• added functionality that handles storing the state of user's policies (wheter a policy was accepted, or not) to database.

New backend files:

• PolicyDeclineController.php - as the name suggests. Basically, it is "1:1 copy" of PolicyAcceptController.php, however with opposite behaviour

Now lets take a look at what changed in the frontend.

Modifications inside Policy.js:

• added optional and additional_info fields to the Policy model.

Modifications inside PolicyEdit.js:

• added new item to fields method, which allows to choose, wheter specified Policy should be optional, or not,
• synced initNewField method with Policy model changes,
• modified deletePolicy method - during developing I encountered a bug - when deleting a Policy, its field is, of course deleted, but also savePolicy method is being called. It was happening possibly because when clicking Delete policy button, onsubmit method is being called.

Modifications inside AcceptPoliciesModal.js:

• added functionality that handles rejecting an optional policy.

Modifications inside `forum/index.js':

• instantiating new addManagePoliciesOption component.

Modifications inside admin/components/index.js:

• exporting new ExtensionData component, so developers working on integrating fof/terms with other extensions could access this component

New frontend files:

• ExtensionData.js - a component that allows developers to integrate fof/terms with other extensions by saving their data into fof-terms-policies table. Recipe on how to use it is descriped in README.md in For developers section.
• addManagePoliciesOption.js - a component that allows users to opt in/out of consents in their profile settings.

Other changes:

• admin.less & new forum.less - added some styling for components,
• en.yml - added translations.
• README.md - added section For developers, explaining step-by-step how to use ExtensionData component, and therefore integrate fof/terms with other extensions.

Reviewers should focus on:

I would definitely want to know, if my instructions on how to use ExtensionData in README.md are specific, exact and free of ambiguities. Every feedback on what in my code can be fixed, rewritten so it is easier to read, or is simply better is greatly welcomed :)

Screenshot

            admin panel - select policy as optional \ \             user settings - opt in/out of consents

Confirmed

• [x] Frontend changes: tested on a local Flarum installation.
• [x] Backend changes: tests are green (run composer test).

Required changes:

• [ ] Related Flarum core extension PR's: (Omit this section if irrelevant)

[AngryDragonite]

All requested changes committed.

[imorland]

Thank you @AngryDragonite - however there are now more files in js/dist. Please remove the dist folder from your commits to resolve the conflicts

[AngryDragonite]

@imorland Sorry for confusion, I followed steps that you advised, but somehow it got worse, possibly because I messed up something. I'm trying to fix it now

[imorland]

@AngryDragonite thanks for your efforts, unfortunately you're now deleting the dist folder contents, rather than simply omitting any changes to them. This should help you ;)

[rafaucau]

@imorland There are changes to the dist folder on the master branch since this PR. Perhaps this is causing the issues? https://github.com/FriendsOfFlarum/terms/commits/master/js/dist?since=2024-04-28&until=2024-06-16

I tried to help @AngryDragonite, but still the files are in this Pull Request.

[rafaucau]

ping @imorland @DavideIadeluca