fix: analytics_logs.node_type should reference text component type rather than integer for new and historic records

[jessicamcinchak]

Changes:

• Alter the column type from integer to text (requires dropping & recreating dependent view)
• Do a one-time update of historic records
• Update analytics provider to insert text / human-readable node_type for all new analytics_logs created

Dependencies:

• Once merged to production, I expect this will break a number of Metabase queries that currently reference the integer node_type in a condition - we'll have to update these independently !

[jessicamcinchak]

Expose human-readable component type in Metabase

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

Perfect! A much better solution that my original thought here 👌

Tested and getting the expected results on Pizza 🎉

[DafyddLlyr]

This has always felt like a bit of a tricky one - if we get feedback that this is oddly named we can very easily update to "Question" or something in future 👍

[jessicamcinchak]

Yep agree - that's probably a change we should consider making at the root type definition rather than just analytics! Hopefully ambiguous text is still a huge upgrade from integer for starters though!

[Mike-Heneghan]

Looks great 🥳