Switch from FileSize to DataSize for Logback size-based properties

[snicoll]

Follow-up of #15325

Our logging.file namespace has two properties that use FileSize behind the scenes. That object is very similar to our new DataSize support so it would be nice to expose DataSize based properties for consistency.

Unfortunately, the format is not 100% the same so we could keep binding to String and do some magic in the code? Or simply move to DataSize.

[nosan]

@snicoll,
I'm ready to start working on this issue, but, I have a few questions:

• Should I change the type of these properties? (String -> DataSize)
• Should I add support for both formats?

Thanks in advance

[snicoll]

The purpose is to support DataSize and pass a long bytes to Logback wherever we can. I can't tell you as I haven't investigated yet.

Unfortunately, the format is not 100% the same so we could keep binding to String and do some magic in the code? Or simply move to DataSize.

The preference is to only care about DataSize but we should investigate first what happens if we use the old (String) format with it