DFS: Refactored IO elements to EzPublishIOBundle

> [EZP-23328](https://jira.ez.no/browse/EZP-23328) (sub-task: [EZP-23380](https://jira.ez.no/browse/EZP-23380))
> Status: WIP

Contains definition of existing (Core) services, as well as semantic configuration for the io handler + definition of the related services.

## Configuration example
```
ez_io:
  system:
    default:
      filesystem
```

Adds a new service tag: `ezpublish.io_handler`, with an alias property for the name of the handler.

## TODO
- [ ] DI tests
- [ ] Remove old files from CoreBundle
Is your config parser really needed ? Given the low complexity of the mapping, a simple closure should suffice I think.