License agreement restrictions must be emitted with restrictive level

[eparovyshnaya]

Currently, if a user has not yet accepted a license agreement, Access Cycle emits restriction of WARN level, and that's confusing.

As the intension is to prohibit an agreement unaware usage of a product or a feature, then corresponding restrictions must have forbidding level (ERROR or FATAL)

[eparovyshnaya]

We always emitt agreement not accepted restrictions with FATAL restriction level.

In this particular case warn appeared in the log because of the feature, that demands this agreement to be accepted. Feature itself declares its own restriction level as warn.

Thus the fix boiled up to log extension. Now unaccepted agreement reported this way:

Agreements state contains 1 entries.
  agreement [licenses/epl-2.0.txt]
  declared by [BaseRequirement [feature=BaseFeature [id=org.eclipse.passage.loc.operator.product, version=2.6.0, name=Eclipse Passage Operator, provider=Eclispe Passage], restriction=warn, source=org.eclipse.passage.loc.operator]]
  has [not accepted] state.
  This is FATAL!11. Product cannot proceed without the agreement been accepted.