[Feature] Adapt acro to be ontology-driven

[jim-smith]

Is your feature request related to a problem? Please describe.
We should start making a branch that where the behaviour is driven by the ontology rather than being hard-coded

Describe the solution you'd like

1. Generate series of dictionaries from the ontology. (this is a one-off task rather than being done for each acro session) and stop as json?
2. those get read into acro as python dictionaries on startup
3. when an acro method that produces a query is called, the tests et that need ot be run are driven by those dictionaries, and the appropriate statements are written into the summary that gets written to results.json when the user calls acro.finalise()

Describe alternatives you've considered
.
Additional context
.

[jim-smith]

ideas sketched from meeting in early Feb

possible_risks:list =  HasRisk[statname]:

is_present:np.array(bool) = [False]*len(possible_risks)

for risk in possible_risks: 

      for check in ChecksForRisk[possible_risk']:

              if run(check):

                  is_present[risk]=True

        if is_present[risk]:

                set_status('Fail')

                 #add possible mitigations for risk to a list of lists

  if any is_present:

         #TODO advise users about mitigation that works for all the rirks detected

          themitigstion= get_users_choice()



           apply(themitigation)

           #v1

          if the_risk in MitigatesFor[thermitigation]

              set_status ("review")

              #not sure about that - might need ot do them all first

        #v2 do the other way round ie 

         if themitigation in IsMitigatedBy[risk]

[jim-smith]

Need to find all risks and checks to run in case pre-selected mitigations are not appropriate