Don't pop ChatInterface variables

[hoxbro]

Without these changes, ChatInterface will not use the new username.

import panel as pn
pn.extension()

pn.chat.ChatInterface(callback=lambda _0, user, _2: user, user="NEW USERNAME")

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (811ccd1) 40.72% compared to head (ad3c846) 84.19%.
Report is 3 commits behind head on main.

Files	Patch %	Lines
panel/chat/interface.py	88.88%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #6290       +/-   ##
===========================================
+ Coverage   40.72%   84.19%   +43.47%     
===========================================
  Files         301      301               
  Lines       45219    45247       +28     
===========================================
+ Hits        18414    38095    +19681     
+ Misses      26805     7152    -19653     

Flag	Coverage Δ
ui-tests	40.71% <18.75%> (-0.01%)	⬇️
unitexamples-tests	71.84% <93.75%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[philippjfr]

@ahuang11 please review.

[ahuang11]

Looks good!

[hoxbro]

Looking at the failing test and a bit at the code. I think there are some possibilities:

1. We promote the parameters user and avatar from Interface to Feed.
2. Inherit send and stream (I think) in Interface and check if they are not set as a keyword argument, set them to the parameter if they haven't been set, and then call super.
3. Update the if statement so we both have them as parameters and in the message kwargs.
4. Maybe another way forward.

I think I like 2 the most.

[ahuang11]

I like 2 too.