OK. Few things to note here.
- The reason why you see the password with  Web Developer - Inspector Tool is because it runs in the very same browser that was used to send the form. The browser and thus the tool knows what was send and helpfully shows that to you. However if your SSL is properly configured, all this information is encrypted before it leaves your browser. Thus no one else can see it while it's being transmitted. This is pretty standard behaviour. Major websites like Facebook and Google work the same way (see screenshots below).
- It is true that inside the data package that is encrypted by the the browser, the password is in plain text. The assumption here is that for someone to be able to see is (while it's being transferred) one has to brake the SSL encryption between the browser and the server. However if that is the case, you have an order of magnitude more serious problem  that the password being not hashed.
- The bank example you've shown indeed uses some kind of hashing for the password field. It is not clear what is the reason for that (it may or may not be related to extra security cautions) nor how exactly it is achieved in this particular case. In general case, for the reasons explained above, it does not provide any extra security.
- Liferay Portal does not provide anything that will hash passwords on the client side (in the browser). If your IT security team insists on doing that for your solution, you will have to do it yourself. You will have to implement this on both client side and server side. How exactly you do that is up to you.Â
