Upgrade nodejs to 18 or 20

[sarahboyce]

nodejs 17 is EOF

This also causes issues for Azure see:
https://github.com/djangonaut-space/wagtail-indymeet/actions/runs/7593041682/job/20683066199
#210

[tim-schilling]

Oh right.

…

On Sat, Jan 20, 2024, 1:56 AM Sarah Boyce ***@***.***> wrote: nodejs 17 is EOF Screenshot.2024-01-20.at.8.55.06.AM.png (view on web) <https://github.com/djangonaut-space/wagtail-indymeet/assets/42296566/22068c86-bb7c-4d7a-ab48-5b3ae994ffdc> This also causes issues for Azure see: https://github.com/djangonaut-space/wagtail-indymeet/actions/runs/7593041682/job/20683066199 #210 <#210> — Reply to this email directly, view it on GitHub <#226>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJYZP44NQ3O4ARLBHZOBFLYPN2CTAVCNFSM6AAAAABCDAM3CSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4TCOJVGQZTSNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[sarahboyce]

With further investigation looks like we need FUNCTIONS_EXTENSION_VERSION to be update to ~4 in order to be able to deploy with an upgraded nodejs https://learn.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal#automatic-and-manual-version-updates

Which I think is an admin action that @dawnwages might be able to do.

I think this because of this failed action: https://github.com/djangonaut-space/wagtail-indymeet/actions/runs/7596711442/job/20690731585

And this related issue: microsoft/Oryx#1844