🛠️ fix: models.InputSticker model handling/usage

[fregin]

Current version of go-telegram/bot does not support createNewStickerSet operation

Because of models.InputSticker struct and its handling in build_request_form.go

If we are trying to create new sticker with such code:

_, err = b.CreateNewStickerSet(
	ctx,
	&bot.CreateNewStickerSetParams{
		...
		Stickers: []models.InputSticker{
	              {
		              Sticker: &models.InputFileUpload{
			              Filename: "myresource.webm",
			              Data: ...,
		              },
		              Format: "video",
		              ...,
	              },
	},
)

You will get next error: Bad Request: video stickers can't be uploaded by URL

But we are uploading file, not URL, are we?

This pull request contains two things:

1. Proper handling models.InputSticker in build_request_form.go
2. Correct struct signature referenced to Telegram API Docs, where models.InputSticker model contains sticker: String field (not sticker: InputFile)

And now we can do this without error:

_, err = b.CreateNewStickerSet(
	ctx,
	&bot.CreateNewStickerSetParams{
		...
		Stickers: []models.InputSticker{
	              {
		              Sticker: "attach://myresources.webm",
		              Format: "video",
		              ...,
		              StickerAttachment: ...
	              },
	},
)

[negasus]

Can you add documentation to readme.md about this method?

[fregin]

Can you add documentation to readme.md about this method?

Sure

[fregin]

There are some restrictions for input sticker files, so I could not find any Telegram logo or Golang logo with .PNG extension and with sizes 512x512 (one size can be less)

Such link will be available after merge

[fregin]

Looks like bot.Bot can store such info, do not you think so?

Maybe create an issue?
But what to do with skip-get-me option? No get me, no info.

[fregin]

Done!