Investigate removing momentjs dependency

[Baldauf]

There are a number of reasons EUI should consider moving away from momentjs, including:

• its global state creates usage hurdles and hard-to-predict code interactions
• there are newer popular date/time libraries which take advantage of newer browser APIs
• momentjs's bundle size isn't insignificant

This thinking aligns with moment's project status page. However, it would be a significant breaking change that would need coordination between internal Elastic teams as well as good communication leading up to changes for outside community users & contributors to respond to.

First steps in the process will be to audit EUI's usage of momentjs and compare that with potential replacement libraries' functionality.

[chandlerprall]

I do expect to see that change in a future version, but there are no plans to do so and that change will need to have larger coordination with other Elastic product teams. We won't be able to explore this change until after our conversion to Emotion (#5685), but it has been a growing source of technical debt and overall a buzzkill knowing there's modern, recommended solutions.

Do you mind if I repurpose this issue (edit the title&description) to track the idea?

[Baldauf]

Thanks for the insight. Yes, @chandlerprall please modify as you wish!

[github-actions]

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

[github-actions]

❌ We're automatically closing this issue due to lack of activity. Please comment if you feel this was done in error.