Initial PR

[3h4x]

what

• created opsgenie submodules
  • alert_policy
  • api_integration
  • escalation
  • notification_policy
  • team
  • team_routing_rule
• every module is tested
• every module has example
• root module as an example module which use all submodules

notes

• disabled superlinter workflow as terrascan error is related to not supporting HCL2 yet. Issue already exist and feature should be soonish released Throwing Errors when parsing nested brackets in HCL tenable/terrascan#233

[danjbh]

I took a pass through all of the modules and spent a bit of time understanding each one -- it all looks pretty straight-forward to me!

[3h4x]

/test all

[3h4x]

My main concern is variable naming. I found redundant to name variable alert_policy with added prefix opsgenie_ but maybe it would be preferred to do that. If such variable would be declared in external system I might find it confusing to see api_integration as not just opsgenie can provide it.
@osterman Any thoughts?