Custom Bank Adapter Class

The challenge is to create a simple Java bank aggregation application that pulls information from multiple different banks and displays it. At the link, you can download some skeleton code I put together to base the solution on. As you will see, there are two packages, [login to view URL] and [login to view URL] which represent proprietary API integration points towards these two hypothetical banks. They only return hardcoded dummy values and ignores input parameters, but I want you to imagine that they represent wrappers for external API calls. They both expose functionality to fetch account balances and transactions, but in slightly different ways. Your solution may not alter these classes. You will also see that there is a class [login to view URL] which is the entry-point for you to start. The challenge here is that I don’t want the BankController to ever directly use any classes in the [login to view URL] and [login to view URL] packages. Instead, you need to create an abstraction layer (using, for instance, an Adaptor pattern) that isolates and “hides” the bank1 and bank2 classes behind a common interface and data structures. Your solution should demonstrate appropriate separation of responsibilities and code isolation. A small hint, as there are different versions of the Adaptor pattern - the point is to create an abstraction that makes bank1 and bank2 look the same, not to create an adaptor that makes, for instance, bank1 look like bank2. I would also like you to include relevant unit tests for the code you develop.