Fix improper quoting on tag values when the value was text

[sparky8251]

Description

Fixes #60

Checklist

• Formatted code using cargo fmt --all
• Linted code using clippy cargo clippy --all-targets --all-features -- -D warnings
• Updated README.md using cargo readme > README.md
• Reviewed the diff. Did you leave any print statements or unnecessary comments?
• Any unfinished work that warrants a separate issue captured in an issue with a TODO code comment

[sparky8251]

Looks like there were clippy lint issues as part of master and I'm unsure if I should fix them. I also tried tests but those seem broken and unable to run as well?

It's likely this change breaks a test though so if its required for merging, just going to need help getting it working so I can fix them (or at least a name of the broken test since the fix should be trivial).

[Empty2k12]

Thanks for fixing the issue 👍 🚀

There should have been a CI run showing which tests fail. I'll check what that didn't trigger.

[Empty2k12]

@sparky8251 I have added a new CI pipeline based on Github Actions and also fixed the clippy issues.

Sadly I do not have maintainer write permissions to your fork, so it would be nice if you could rebase to the latest master and have CI tell us which tests are incorrect.

[sparky8251]

Ok, All the clippy lints and tests pass now.

The query::write_query::tests::test_escaping test was especially brutal and I'd spend 90% of the review time on that test as while I've got it passing, I'm only 99.9% certain I retained the initial intent behind the test given all the rando backslashes and double quotes in so many places.

Squashed down all my test attempts so its just 2 discrete commits. If you want 1, let me know.

[Empty2k12]

Taking a look now! Thanks for rebasing!

The query::write_query::tests::test_escaping test was especially brutal and I'd spend 90% of the review time on that test as while I've got it passing, I'm only 99.9% certain I retained the initial intent behind the test given all the rando backslashes and double quotes in so many places.

Honestly InfluxDb line protocol is very painful. As this PR uncovered, my initial implementation is not correct even though I based the escaping parts and tests off of the official Go package.

[Empty2k12]

From what I can tell, the new behavior looks correct. All types of escaped tested in the go sdk are covered.

Thanks for creating this PR and helping make this crate better.

[sparky8251]

No problem! Using this crate to pull sensor data from embedded devices and this was something that bit me. Ended up making it incompatible with other libraries and methods of inputting data into influxdb so I had to fix it :)

[Empty2k12]

I think this change will be pushed to crates.io when #62 is merged. Until then, you reference this repo directly by Git.

If you come across further problems, feel free to open issues or pull requests addressing them. All improvements appreciated.