feat(NETWORK_INFORMATION): add new token

[thekiba]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows Conventional Commits
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[waterplea]

I wonder if it should be named NETWORK_INFORMATION or CONNECTION. @MarsiBarsi what do you think?

[thekiba]

@waterplea NETWORK_INFORMATION is more informative for me instead of CONNECTION 😁

Please check the pr again, I force pushed the changes

[MarsiBarsi]

both options are okay for me 👍

[thekiba]

@waterplea I have reverted the change of returns undefined instead of null in the token factory for the tests to pass

[waterplea]

@thekiba instead you can add a second test where you would mock NAVIGATOR token with an object missing connection property. Test would be: "Injects null in unsupported browsers"

[thekiba]

It's a success now 🙌

[waterplea]

All looks well now. I wonder if there's a way not to force everybody to install those types if they do not use this token 🤔

[waterplea]

@MarsiBarsi what if we bundle it? It's just types, shouldn't really matter. What do you think?

[MarsiBarsi]

@waterplea I think it is a good idea. Let's make the type with "TODO to remove" after adding TS support

[waterplea]

Took the liberty to do those changes, related to types bundling. Looks like it works fine now, I tried a pre-release version on my pet project. Thank you, @thekiba !