Behat: Isolated institutions scripts needed

TITLE: Behat: Isolated institutions scripts needed for new functionality

BEHAT SCRIPT : Create Script feature file ->isolated_institutions.feature

RELATED TO: https://bugs.launchpad.net/mahara/+bug/717196
https://bugs.launchpad.net/mahara/+bug/1832308
https://bugs.launchpad.net/mahara/+bug/1823065
https://bugs.launchpad.net/mahara/+bug/1831835
https://bugs.launchpad.net/mahara/+bug/1748833

SUMMARY: Isolated institutions is a feature that allows locking down access for members of institutions so that they are separated entirely and disallow contact between members of one institution with members of another institution.

REQUIREMENTS: By turning on isolated institutions,

1) all institutions on the site are isolated
2) people from different institutions cannot
a) see each others’ profiles
b) share portfolios
c) join groups set up by non-institution members
d) send messages
e) become friends
f) only site administrators can contact everyone
3) being a member in multiple institutions is not possible
4) all self-registrations need to be confirmed by an institution or site administrator
5) public groups can only be created by site administrators
6) the “Online users” side block can only show institution members at maximum
7) profile pages are not available to all registered users
8) The site administrator can turn on the site setting “See own groups only” in Administration menu → Configure site → Site options → Group settings. This will allow regular institution members to only see groups in which they are a member and other people who are members in the same groups, restricting the contact they can have with others.
9) Institution administrators decide in the institution settings whether the online users side block shall be displayed with just the institution members or not.
10) When an institution member gains access to a profile URL from another institution member, they cannot see the page at all and receive the “Access denied” message, preventing them from even seeing the restricted profile as they should not be able to find out anything about a member of another institution.

*********************************************************************************
Suggested Scenarios:

Test Scenario: When Isolated institutions are turned on, The “Multiple institutions” option is disabled & The “Confirm registration” option on the site level is turned on per default

Test Scenario: people from different institutions cannot
  a) see each others’ profiles
  b) share portfolios
  c) join groups set up by non-institution members
  d) send messages
  e) become friends
  f) only site administrators can contact everyone

Test Scenario: being a member in multiple institutions is not possible

Test Scenario: all self-registrations need to be confirmed by an institution or site administrator

Test Scenario: public groups can only be created by site administrators

Test Scenario: the “Online users” side block can only show institution members at maximum

Test Scenario: profile pages are not available to all registered users

Test Scenario: The site administrator can turn on the site setting “See own groups only”

Test Scenario: Institution administrators decide in the institution settings whether the online users side block shall be displayed with just the institution members or not.

Test Scenario: When an institution member gains access to a profile URL from another institution member, they cannot see the page at all and receive the “Access denied” message, preventing them from even seeing the restricted profile as they should not be able to find out anything about a member of another institution.