Airplane Group Spawning

[Wizxrd]

Initial implementation of spawning an airplane group from an airbase, zone, or lat lon coordinate with any number of points. When spawning from an airbase you have the option to spawn hot, cold, runway and in air.
Individual unit payloads are yet to be implemented as are taskings for each point in the route. These can be complex tasks to get done properly, so need to think about how it should be done easily for the end user.

added createPlaneGroupTemplate
returns a table required to spawn an airplane group

added createPlaneGroupUnitsTemplate
return a table of units needed to spawn an airplane
prepares units to spawn from an airbase, zone, or lat lon
if spawned from an airbae options are hot, cold, air, or runway

added buildAirplanePoints
return a table of built points for airplane groups
points are based around vec3's that can be from zones, airbases and lat lon

notes:

• when spawning an airplane from an airbase that is a ship it is required to use the unit name as the place
• the place within units is the inital spawning place of the units
• changed the addGroup method to include being able to pick a differnt tempalte based on params.template.type
• types could be "Ground" "Helicopter, "Airplane", "Sea" if implemented that way

** Example Usage in Lua **

local groupTable = createPlaneGroupTemplate({
  groupName = "Hornet 1",
  task = "CAP",
  points = {
    {
      alt = 2000,
      alt_type = "BARO",
      place = "Naval-1-1", -- ship unit name
      type = takeoffTypes.hot,
      action = takeoffActions.hot,
      speed = 250,
    },
    {
      alt = 2000,
      alt_type = "BARO",
      place = "zone1",
      type = "Turning Point",
      action = "Turning Point",
      speed = 250,
    }
  },
  units = {
    -- these are required to be the same
    place = "Naval-1-1", -- ship unit name
    type = "FA-18C_hornet",
    alt = 4000,
    alt_type = "BARO",
    speed = 250,
    {
      unitName = "Hornet 1-1",
      skill = skill.Random,
      --parking =
      --parking_id =
      --callsign =
      --skill =
      --livery_id =
    },
    {
      unitName = "Hornet 1-2",
      skill = skill.High,
      --parking =
      --parking_id =
      --callsign =
      --skill =
      --livery_id =
    }
  }
})
coalition.addGroup(country.id.USA, Group.Category.AIRPLANE, groupTable)

[rurounijones]

Been talking to Wizxrd in Discord about this looking at this.

Added some comments that could be fixed now while I ponder what we can do in the gRPC layer to simplify things.

[rurounijones]

I'll think about if we can do this in a different way by having gRPC types. No need to change this for the moment, just an FYI.

If may be that we do not allow clients to specify anything other than a Lat/Lon/Alt point since the client can get the information on airfield locations and zones themselves and send us that data instead of making us find it server-side.

[rurounijones]

On reflection I think we should only allow Lat/Lon/alt using the Position Protobuf message. Clients should be able to get all the information they need to be able to popualte this information themselves and it simplifies the lua a lot.

[rurounijones]

Again as an FYI this bit may change, but nothing to do yet.

[justin-lovell]

Howdy @rurounijones and @Wizxrd ! I am interested in this feature being added to the core project; and I can't find Discord link anywhere so I can't follow up on that channel -- is there something I could do to help with this first push, and follow up with additional work? E.g. Ships.

[rurounijones]

We are using the OverlordBot Discord for this (Don't want to setup another project specific Discord). https://discord.gg/9RqyTJt

I am busy with OverlordBot stuff at the moment, but there was a bit of discussion in the #developers channel of the gRPC category of that Discord. So you can have a look there.

Basically it was, as far as my memory goes, what changes we can make to this to abstract some things at the gRPC level using existing constructs (e.g. using a Position construct instead of sending lat/lon at the gRPC level)

See also: #76 for other discussion