feature: add yzma llm support

[deadprogram]

This PR is to add support for using yzma to call llama.cpp libraries directly from a langchaingo application.

If the idea seems good, I will do some additional work to add some docs and also make sure the tests pass on the CI. I do have the tests for the new subpackage passing on my local machine, as well as being able to run the new example:

$ go run .                                       
A square has four sides, each with equal length and opposite to each other. This means that the sum of the lengths of any two sides is always equal to the length of the side opposite to the vertex opposite to the
 vertex. Mathematically, this can be expressed as a^2 + b^2 = c^2, where a and b and c are the lengths of the sides, and a and b are the diagonals of the square.
                                                                                                          
This formula holds true for all squares, regardless of their size, because it's a property of squares that they're symmetric about their diagonals. The reason for this symmetry is that a square's diagonals bisect
 each other, meaning they're perpendicular bisectors. This means that if you draw a diagonal from one vertex to another vertex, it's always perpendicular bisector to the diagonals of the squares adjacent to it.
                                                     
This property of squares is a fundamental aspect of their geometric properties and shapes, and it's why squares appear so ubiquitous in geometry and architecture.

PR Checklist

• Read the Contributing documentation.
• Read the Code of conduct documentation.
• Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
• Describes the source of new concepts.
• References existing implementations as appropriate.
• Contains test coverage for new functions.
• Passes all golangci-lint checks.