Fix ec2_launch_template to correctly remove all None types

[stefanhorning]

fixes issue #230

SUMMARY

When leaving module params blank the module would send None types in it's nested dics structure to boto, which then led to errors
This PR is fixing this by recursively removing all None types from the entire dict passed to boto.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

ec2_launch_template module

ADDITIONAL INFORMATION

Run this task for example with and without the fix and you will see what I mean:

    - name: Create Launch Template to test Ansible ec2_launch_template module code
      ec2_launch_template:
        name: test-ansible-ec2-launch-template-module
        image_id: ami-XXX
        security_group_ids:
          - sg-XXXX
        instance_type: c5.large
        key_name: my_key
        instance_market_options:
          market_type: spot
          spot_options:
            max_price: 0.5
            spot_instance_type: one-time
            instance_interruption_behavior: terminate
        block_device_mappings:
          - device_name: /dev/sda1
            ebs:
              volume_type: gp2
              volume_size: 10
              delete_on_termination: true
              encrypted: true
          - device_name: /dev/sdb
            ebs:
              volume_type: gp2
              volume_size: 200
              delete_on_termination: true
              encrypted: true
        monitoring:
          enabled: false
        region: us-east-1
        state: present
      register: launch_template_result

    - name: Output result
      debug:
        var: launch_template_result

Of course replace XXX with your IDs. Find more test cases in #230

[stefanhorning]

Actually there is a second issue here #251 which is a duplicate of #230. Thus this PR fixes both issues.

[ansibullbot]

cc @jillr @s-hertel @tremble @wimnat
click here for bot help

[markuman]

It's big chaos about the None values...the idea was a module_utils function in amazon.aws, that can be used all over the aws collection.
I guess you should close your merge request and become an active reviewer for this PR ansible-collections/amazon.aws#262 to speed things up.

[stefanhorning]

yes, I realized that by now. Just missed the final PR at first :)