Magento 2.3.5 migration - Category IDs not correctly set in corresponding tables. (Fix related to error 404 / Knockout bindings not working)

Nobody has claimed this yet.

### Preconditions

1. Magento 2.3.5 clean installation
2. Magento Data Migration tool v2.3.5 with config for source data Magento 1 : 1.7.0.2

### Steps to reproduce

1. Setup clean installation of Magento 2.3.5
2. Migrate Data but make sure to rename Magento 2.3.5 attribute set names (otherwise this tool complains and fails with DUPLICATE IDs)
3. After renaming existing M2 attribute set names migrate M1 data.
`bin/magento migrate:data path/to/config.xml`

### Expected result

1. A working Magento 2 setup with migrated data.

### Actual result

Besides other issues also failing (not related to this discussion), the **category's are not editable in the backend, category data is not bound (only default data shown), frontend category landing pages also not working (missing)!**

### Issue
Data migration tool does **not import and fill database tables correctly** when 'Default' attribute set is also in source database. _Only partially fills database correctly._

Database tables `catalog_category_entity` and `eav_entity_attribute` are involved with this issue.

# Solution - Database side
The full question and solution (from database side) is on my topic here:
[Magento Stack Exchange solution](https://magento.stackexchange.com/questions/313280/solved-magento-2-3-5-category-backend-data-binding-not-working-category-fron/313384#313384)

It would be great if this can be applied on the data-migration-tool directly.

(I have to do alot of things over and over when reimporting, including this).

Start by reproducing the migration with Magento 2.3.5, the Magento 1.7.0.2 source, and bin/magento migrate:data path/to/config.xml. Inspect catalog_category_entity and eav_entity_attribute after migrating with renamed attribute sets, then use the linked Magento Stack Exchange solution as the behavior reference. Done means migrated categories are editable in the backend and their frontend pages and bindings work.

Written by the indexing model from the issue text.