[ISSUE-278] Resolve pipeline_metadata.version error

[RobsonSutton]

• Raised to resolve - [Bug] Logstash pipeline pipeline_metadata.version read is failing  #278
• [Breaking Change] Change type of pipeline_metadata to schema.TypeString - This setting throws an error when the pipeline is updated manually, as the subsequent terraform plan cannot handle the version value being of type: float64.
• Update docs to reflect COB-3434: Updated queue.max_bytes with unsupported number and units #291
• Reorder Logstash pipeline tests to match the order they are being checked in

[RobsonSutton]

@tobio - Hey, another small one for when you have a spare min or two 👍

Unfortunately I couldn't find a way to handle multiple data types in TypeMap... (please do enlighten me if this is possible though!)

Have also just deprecated the field as opposed to introducing a breaking change by replacing, so technically the error still exists in the old pipeline_settings, but this should provide a workaround for those that may run into it until the older field is fully removed

[tobio]

I'm inclined to just make this a breaking change. It seems like the current field will crash the provider quite easily, and migrating to the new schema is relatively simple (i.e wrap in jsonencode()).

@Kushmaro do you have an opinion here?

[tobio]

I'm inclined to just make this a breaking change.

@RobsonSutton, lets do this. It's nicer to break this now and completely close of this bug.

[RobsonSutton]

@tobio - Should be updated to be a breaking change now 👍

[tobio]

LGTM 🎉 thanks for tidying this code up :)