Lua scenarios where configuration parsed incorrectly

[oliveromahony]

Proposed changes

An issue was discovered when parsing configurations with ssl_certificate_by_lua_block in them. This is intended to add a fix and tests covering those scenarios

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING document
• If applicable, I have added tests that prove my fix is effective or that my feature works
• If applicable, I have checked that any relevant tests pass after adding my changes
• I have updated any relevant documentation (README.md)

[xynicole]

{"\n            print(\"Test lua ssl certificate!\")\n        ",5},
		{";", 5},

We grab everything in the Lua block as a single token and drop the {}. Example:
content_by_lua_block {some code} will be content_by_lua_block "some code"; "some code" is an argument of directive.

For reference: #86

[xynicole]

Suggested change

	{"\n print(\"Test lua ssl certificate!\")\n ", 19},
	{")", 20},
	{"}", 21},
	{"\n print(\"Test lua ssl certificate!\")\n ",21},