Avoid recreating tables in acceptance specs

It turns out these specs were reliant on transaction isolation anyway and the transaction does not seem to get in the way of communicating with CC

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Default runtime AppSecurityGroups are associated with all spaces

* New AppSecurityGroupsSpace object to represent the join table between spaces
  and app security groups
* Needed to specify the dataset and eager_loader associated with the many_to_many
  relation between spaces and app security groups as the defaults are now
  included.

[#71584908]

Signed-off-by: Joseph Palermo <jpalermo@pivotallabs.com>
Remove unused creation_req and update_req code from controller specs

Signed-off-by: Joseph Palermo <jpalermo@pivotallabs.com>
User visibility for app security groups

[#72119904]

Signed-off-by: Joseph Palermo <jpalermo@pivotallabs.com>
Avoid pollution between examples by using separate models

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Use conventional class syntax

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Spec was subtly reliant on test-pollution

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Avoid accidentally relying on test pollution

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Always use truncation instead of recreating tables

truncation is usually faster

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Extract non-bootstrap code from SpecEnvironment

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Make fixture path a global constant

Since it never changes and always has the same value

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Delete unused code

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Replace global mixin GlobalHelper

- Extract its parts into TestZip and TestConfig
- Explicit receivers make it much easier to find method usage and definition

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Avoid more widely-scoped mixins

- Also organize files in spec/support since there are getting to be quite a few things in here
- We are trying to avoid mixins in favor of explicit receivers to make usage more transparent

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>