llms: Add fake package

[devalexandre]

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.

[eliben]

You checked " Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).", but in fact it's not clear at all what and why this is doing.

Also, the code is full of Portuguese comments and strings, is this intentional?

[devalexandre]

You checked " Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).", but in fact it's not clear at all what and why this is doing.

Also, the code is full of Portuguese comments and strings, is this intentional?

sorry , I'll update to en and edit the list

[flc1125]

I suggest adding a Generate interface to pass in, instead of responses []string.

Then implement a Default Generate to support it. This would allow for better customization and extensibility.

[tmc]

LGTM. would be cool to support streaming.

Please leave source comments in english

[tmc]

LGTM