I got the impression from your colleagues, based on previous questions/answers that mobile devices were not your primary target. I came to this conclusion because I repeatedly pointed out that Ionic was optimized for apps delivered to mobile devices and thus, the UI elements have been designed for touch, so changing the sizes of headers, buttons and other touch-targets was not advised. I further pointed out that large grids of tabular data was not conducive for display on mobile devices and produces very poor usability.
I never got an explanation as to why you were continuing with your design approach despite these points, so, I was left to assume that mobile devices are not your target. If that is correct (that you're not designing a mobile or responsive app), then here are some options:
Use a table. I've recommended this previously to Pallavi. Given that your data is tabular in nature, a table makes a lot of sense. Furthermore, there are solutions like UI Grid that can offer some out of the box support for dealing with complex data sets and provides many built in features for column sorting and searching, pagination, grouping and summary rows. It's a bear to use, but depending on your requirements, it's worth knowing about (again, assuming you're not building for mobile).
Do not use collection-repeat and choose ng-repeat instead. The collection-repeat directive is designed for delivering large data sets to mobile devices. The intent is to provide better performance on lower powered devices with smaller screen resolutions. As a result, collection-repeat ONLY renders the collection items that are current in view. In order to do that efficiently, the directive needs to have a consistent row height so that it can calculate the number of visible items. I tried and tested several approaches to get around this, but in the end the simple answer was the most performant: Use ng-repeat instead. You can vastly improve performance of ng-repeat with the use of one-time bindings and filters that can make up for the performance gains offered by collection-repeat.
Especially if I'm wrong about the mobile part, then you should consider that the third option is to change your UI vector entirely. It's none of my business, but I do have 25 years of experience designing and building enterprise software products, so I'd be remiss if I didn't point out that your current UI design is nothing more than a non-functional version of MS Excel. Where is the benefit for the user? How does seeing some 5000 records in a paginated grid help them to act on that data in the context of their job? Personally, I would revisit my personas (or actual user stakeholders), and ask those two questions. You might find that the best approach is to scrap everything and replace it with some other UI (such as a search interface or a list interface). I did in fact mock up two alternative approaches, but after testing, I decided that the effort and additional bindings didn't make sense in the context of a desktop application. So, again, in the context of what I understand your requirements to be I recommend the two options above.