frontend: fix /build/source-chroot/ endpoint

[FrostyX]

As reported by @nforro, this tracebacks because of not existing endpoint.

from copr.v3 import Client as CoprClient
copr_client = CoprClient.create_from_config_file()
copr_client.build_proxy.get_source_chroot(8481944)

For some reason this endpoint was renamed from /build/source-chroot to /build/source-log in 7455d47. I suppose it was a typo?

[FrostyX]

I hotfixed it as

--- /usr/share/copr/coprs_frontend/coprs/views/apiv3_ns/apiv3_builds.py 2024-10-03 00:00:00.000000000 +0000
+++ /usr/share/copr/coprs_frontend/coprs/views/apiv3_ns/apiv3_builds.py 2025-01-07 18:08:35.015963178 +0000
@@ -187,6 +187,7 @@


 @apiv3_builds_ns.route("/source-log/<int:build_id>")
+@apiv3_builds_ns.route("/source-chroot/<int:build_id>")
 class SourceChroot(Resource):
     @apiv3_builds_ns.doc(params=get_build_docs)
     @apiv3_builds_ns.marshal_with(source_chroot_model)

(not removing the currently deployed route, only adding the previous one)

[xsuchy]

+1

[praiskup]

waiting for @nikromen to review this (might be an intentional change)
praiskup tends to keep the old path, just in case

[nikromen]

oops, sorry. Yes this seems like a typo, if I needed to intentionally change it, I'd deprecated the old endpoint to not break backward compatibility (like with some REST API methods in our docs). Thanks!

[praiskup]

On Frontend:
for i in access_log-202*; do gunzip < $i | grep /source-log/; done

No hit; apparently no one visits the old path (no need to keep the backward compat). Merging.