Refactor executable IDs to use strings #262

This commit unifies executable ID structure across categories and
scripts, paving the way for more complex ID solutions for #262.
It also refactors related code to adapt to the changes.

Key changes:

- Change numeric IDs to string IDs for categories
- Use named types for string IDs to improve code clarity
- Add unit tests to verify ID uniqueness

Other supporting changes:

- Separate concerns in entities for data access and executables by using
  separate abstractions (`Identifiable` and `RepositoryEntity`)
- Simplify usage and construction of entities.
- Remove `BaseEntity` for simplicity.
- Move creation of categories/scripts to domain layer
- Refactor CategoryCollection for better validation logic isolation
- Rename some categories to keep the names (used as pseudo-IDs) unique
  on Windows.

tests/unit/application/Parser/CategoryCollectionParser.spec.ts

@@ -66,7 +66,10 @@ describe('CategoryCollectionParser', () => {
           getInitParameters,
         } = createCategoryCollectionFactorySpy();
         const actionsData = [getCategoryStub('test1'), getCategoryStub('test2')];
-        const expectedActions = [new CategoryStub(1), new CategoryStub(2)];
+        const expectedActions = [
+          new CategoryStub('expected-action-1'),
+          new CategoryStub('expected-action-2'),
+        ];
         const categoryParserStub = new CategoryParserStub()
           .withConfiguredParseResult(actionsData[0], expectedActions[0])
           .withConfiguredParseResult(actionsData[1], expectedActions[1]);