In the linked support case SUPPORT-4669 there is a nice screen cast showing this behavior.
I can confirm the same behavior.

reproduce:
1. Upload an image directly as assets. -> Node name does not contain the suffix
2. Zip the same image and do a "Zip Upload" of it. -> Node name does contain the suffix

The behavior should be aligned for both cases.

I'm not sure which one of the cases is the goal for the future:

• Having the suffix in the node name
• Not having the suffix in the node name

I'm in favor of having the suffix in the out of a simple reason:
I've seen in many projects, that they need to provide files with the same names but different extensions, for example:
A movie file and its cover file (.mov & .jpg) must usually have the same name.
Or different images in different qualities/formats:
image.tiff (the original high quality, could also be .bmp)
image.jpg (one with no alpha channel
image.png (one with alpha channel)

As long the suffix is not in the file name this can't be achieved.

I'm aware that this impacts the link creation.
If you have the suffix in the file name then the link creation has two times the suffix in it: once form the node name, once form the file extension property of the asset, see print screen "The Two URLs.png".
So the cases should be aligned and the link creation should take account of having the suffix in the node name (and then ignoring the file extension within the asset), or something alike.