Prepare a presentation/demo for stakeholders

[PawelLipski]

Also @Gryfit:

• [x] add a mention to README how to use this library (i.e. at this point, how to refer to this stuff via sbt using jitpack.io Maven repository)

• [x] possibly I missed that during the dry run of https://slides.com/bartektonia/tensorflow-dotty#/3/1, but I think if we bring the Layers, they can/should be explained more accurately

• [x] as for the presentation title/link: I'd rather use Scala 3 than Dotty; the former name 1) sounds more stable 2) is more future-proof if it comes to reusing this presentation

• [x] I'd possibly add an explicit use case where Scala API excels over the vanilla Python API (esp. wrt. easy-to-miss typing errors or so) - but that' s just a nice-to-have, in this presentation we're preaching to the already Scala-converted anyway

• [x] model.add invocations in Examples look kinda awkward given this is a Scala API... maybe provide a c'tor to me.shadaj.scalapy.tensorflow.keras.models.Models#Sequential that accepts varargs of Layers

• [x] expand on why scala 2 remained in the project

• [x] add introduction (goal, background information)

• [x] add closure (performance, results)

• [x] slides 4.3, 5.3-5.6, 6.2, 6.3, 7.2: redundant scrollbars for snippets

• [x] slide 7.4: word native is confusing, maybe just scala.Using

• [x] side by side view of examples

• [x] slide 2.2: credit the original author using his full name

• [x] slide 4.2: is it complicated macros or rather unstable/incomplete macros API in Scala 3? :thinking: anyway, the former ("we didn't do it and preferred to introduce a significant code repetition coz it was complicated") looks a bit... ungeeky :nerd_face:

• [x] slide 4.5: mention performance test results

• [x] slide 4.4, 6.3, 6.5: redundant scrollbars (maybe it can't be turned off/is screen-dependent :/)

[Gryfit]

https://slides.com/bartektonia/tensorflow-scala3

[PawelLipski]

For record: https://slides.com/bartektonia/tensorflow-scala3 is the new URL