Auto populate bot avatar for webhook integrations bot

[PieterCK]

🗒️ Overview

This proposal aims to enhance the bot avatar feature by automatically assigning a bot avatar to incoming webhook bots based on the integration app they are associated with.
This feature was originally discussed in:
Issue #692
PR #12474

CZO discussion: here

Save the integration field to BotConfigData.

• To start, add another "Select an integration" dropdown field to the bot creation modal (add_new_bot_form.hbs).
• Save the selected integration from the bot creation modal using BotConfigData probably in the same manner as how Embedded bots save their service_name.

Make integration field update-able in Backend.

• Pre-populated the original "Select an integration" field in the generate URL integration modal (generate_integration_url_modal.hbs) with the selected option during bot creation.
• Every time "Select an integration" field change, make calls to the backend to change the value in BotConfigData. A good reference mightbe over at Settings where we save on field change instead of clicking a "save" button somewhere.

Auto Assign Bot Avatar

• Auto-assign bot avatar to incoming webhook bots with the selected integration. This could be done in endpoints such as add_bot_backend() to auto-assign the bot avatar when the bot is created. There may be better ways this could be achieved

mock-up of the new bot creation modal:

Before	After
	pre-populated when opened

Follow up

• The second "Select an integration" dropdown field in the generate URL integration modal could be removed. This step will need to be confirmed again once the proposed changes have been implemented. CZO discussion

[PieterCK]

@zulipbot add "area: bots"

[zulipbot]

Hello @zulip/server-bots, @zulip/server-integrations members, this issue was labeled with the "area: integrations", "area: bots" labels, so you may want to check it out!

[Mukul1235]

I would like to work on this issue

[Mukul1235]

@zulipbot claim

[zulipbot]

Hello @Mukul1235, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

[Mukul1235]

Hello @Mukul1235, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

I had completed the work on that issue. this issue is ready for maintainer review

[PieterCK]

Hello Mukul, thanks for picking up this issue. You might want to catch up on the discussion in the CZO if you haven't already. There were some small details I haven't updated in the issue description. I'll update it in a moment

[PieterCK]

Updated PR description.

This issues' scope is quiet wide. I think it might be a good idea to start your PR by only addressing the first couple of point first..

Feel free to ask in the discussion at CZO if you have any questions,

[Mukul1235]

Hello @PieterCK
yeah sure..thanks