Cleaning up Architecture a bit more with Model with properties that backs the Fx GUI.  And moved sample data into this (just a test for now).

The 'New Portfolio' button works and adds to backing Property on the model.
I originally wrote the persistence / Portfolio.java @Entity as a JavaFx model with Properties.  It didn't work as Properties aren't serializable, so I reverted and planned to use a DTO to load between the model and database.  I realised something and moved the @Id from the 'long id' to the 'getId()' and then suddenly the persistence not happening on the property but the getters that return a string.  So this works now and don't need to have separate model and persistencee entities.  However I always planned to have some separation so that I can quite easily convert to using a WebApp with web services to deliver the data instead of it coming from a local Db.

What I think I'll do here is retain the Model and Persistencee, and put a backend implementation specific DTO (based on an Interface which I already have - its PortfolioLoader) which for the current arrangement with a local DB will have the two properties (ie. one for each at each end) mirror the other like properties do.  I'm not sure if you can do this so will do some investigation.

Anyway, this commit is having the new persistence/Portfolio.java @Entity that is composed of properties.
1. Added crud service
2. Added service factory (and again something that it, or what it returns, that should be @Injected - a TODO)
3. Added a 'portfolioLoader' class to sit between the model and persistence (or model and whatever else such as RESTful web services) though changed the plan and just connecting directly to a local DB.  I will re-architect to allow for different data sources in a later version.
4. Fixed portfolio table data to come from the persistence model and for there to be binding between them of sorts, so database mods seen immediately.
5. Added namedqueries() to Portfolio enity and using to retrieve data (using PortfolioService).
6. Oh, added a PortfolioService which extends an abstractService.  This provides a general mechanism to wire it all together from dB to UI.

TODO:
1. Cleanup - such as don't need model/Portfolio.java so may just move the persistence/Portfolio.java into here instead
2. Cleanup - Remove the portfolioLoader structure
3. Modify Portfolio entity to have Many to Many with Stocks
1. Cleaned up Portfolio.java.  Retained the persistence/Portfolio.java as that seems most appropriate.
2. Cleaned up some superflous classes and references that are not needed.

TODO:
1. Modify Portfolio entity to have Many to Many with Stocks