Co-authored-by: Eduardo Navarro <enavarro@suse.com>

Drop the minitest test

Co-authored-by: Eduardo Navarro <enavarro@suse.com>

There are two types of trigger routes:

On /trigger you can trigger an type of `Token`
On /trigger/[rebuild, release, runservice, workflow] you can trigger only this type of `Token`

If a `Token` has a `Package` the operation is executed on this `Package`.

If a `Token` does not have a `Package` you can set one via the project/package
parameters and the operation is executed on this `Package`.

If a `Token::Rebuild` or a `Token::Release` has no `Package` you can set a
`Project` via the project parameter and the operation is executed on this
`Project`.

Co-authored-by: Adrian Schröter <adrian@suse.de>
Co-authored-by: Eduardo Navarro <enavarro@suse.com>

Move spec/support/shared_* to spec/shared

Merge pull request #15390 from openSUSE/dependabot/github_actions/dawidd6/action-download-artifact-3

Drop cassette rewinder

These are not supporting the test suite, these are just
shared contexts/examples...

Instead of code_mirror_helper that requires support/code_mirror...

No one is using this anymore...

Drop spec/rails_helper.rb

Allow users to subscribe to reported requests events

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3 to 4.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v3...v4)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact) from 2 to 3.
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](https://github.com/dawidd6/action-download-artifact/compare/v2...v3)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

There is not a single spec that does not require spec_helper AND rails_helper.
Guess this separation did not pan out....

Fix typo

Revert "Add email subscriptions for decision related events"

Ensure all reports of a Decision point to the same reportable 

Add decision events to subscription configuration form 

Stop creating reports if decision has more reports pointig towards
different reportables

This reverts commit 9eceba62.

We should not create default subscription through a data migration,
this is up to the OBS admin to configure. We now have those events
integrated in the subscription configuration UI. Lets drop this
data migration again.

 Use file_fixture for file fixtures 

RSS is not supported for those events.

Users that are participating in the content_moderation beta
program should be able to configure those subscriptions.
Admin should always be able to configure them for the defaults.

Implement an event to detect request reporting

No need to re-invent the standard...

https://api.rubyonrails.org/classes/ActiveSupport/Testing/FileFixtures.html#method-i-file_fixture

Add subscription form for `Event::AppealCreated` for moderators and admins

Creates the event required to notify the event subsystem of the creation
of a Reported BsRequest.

Report a request

We only need one location for file fixtures.

Similar to the `Event::ReportFor...` subscriptions, the
`Event::AppealCreated` is only interesting for content
moderators.
In the Admin subscription configuration interface (for default
subscriptions) we also going to show it.