Remove desugaring from this project

[Jaehwa-Noh]

What I have done and why

We can remove desugaring from this project.
The only usage of desugar API is just here.

nowinandroid/core/ui/src/main/kotlin/com/google/samples/apps/nowinandroid/core/ui/NewsResourceCard.kt

Lines 242 to 247 in 85129e4

	@Composable
	fun dateFormatted(publishDate: Instant): String = DateTimeFormatter
	.ofLocalizedDate(FormatStyle.MEDIUM)
	.withLocale(Locale.getDefault())
	.withZone(LocalTimeZone.current.toJavaZoneId())
	.format(publishDate.toJavaInstant())

When we remove the desugaring, we can remove androidDesugarJdkLibs dependency.
Output APK's size is reduced 1MB.

And there's no need to use JAVA 11 whether even use the desugaring, the JAVA version bumped at #1392 PR

[yogurtearl]

DateFormat is not thread-safe or immutable and DateTimeFormatter is.

ideally, the formatter would be remember'd (and thread-safe and immutable)

[Jaehwa-Noh]

Thank you to review it.
Let me says my opinion.

I checked the java documentation, it said

Synchronization

Date formats are not synchronized. It is recommended to create separate format instances for each thread. If multiple threads access a format concurrently, it must be synchronized externally.

I don't think my DateFormat is called on multiple thread, it's only called on main thread.
And It has been created new DateFormat instance as NewsResourceCardExpanded is composed.

[alexvanyo]

We use desugaring in a lot more places than just that one with our usage of kotlinx-datetime for time APIs on older SDK versions. This PR will crashes at startup on an API 21 device.

Using desugaring adds size to the APK (like any library), but for our minified release it is around 0.2 MB, which seems well worth it to be able to use much better time APIs.