Fix tests on Julia 1.10+

[mortenpi]

Alternative to #167. It looks like there has been a bugfix in 1.10, and the auto-generated methods when you have positional arguments with default values:

DocStringExtensions.jl/test/TestModule/M.jl

Line 7 in ec66ad4

g(x = 1, y = 2, z = 3; kwargs...) = x

On 1.9:

julia> methods(M.g)
# 4 methods for generic function "g" from Main.M:
 [1] g()
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [2] g(x)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [3] g(x, y)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [4] g(x, y, z; kwargs...)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7

vs on 1.10:

julia> methods(M.g)
# 4 methods for generic function "g" from Main.M:
 [1] g(; ...)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [2] g(x, y, z; kwargs...)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [3] g(x, y; ...)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7
 [4] g(x; ...)
     @ ~/juliadocs/clones/DocStringExtensions.jl/test/TestModule/M.jl:7

So I would argue that the new printing is more correct actually, and so we should instead make the tests version-conditional.

It wasn't obvious to me if there's any way to support the new printing on older Julia versions -- it looks like the information about the kwargs is just missing from the method metadata. It would be good to know which PR in Julia changed this though.

Also makes the CI to run weekly on a schedule, so that we'd maybe catch nightly regressions earlier.

[MichaelHatherly]

Does a failure here notify anyone within the org @mortenpi?

[mortenpi]

Good point. I think it will notify whoever is the author of the last commit, which might not be ideal.

[mortenpi]

Actually, it looks like it's the person who changes the cron line:

Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, see "Notifications for workflow runs."

Which would be me right now, which seems fine.

• https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule
• https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/notifications-for-workflow-runs

[fredrikekre]

https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#github-actions-notification-options I think it will notify the people that actively subscribe to e.g. failed runs? I don't think that is turned on by default.

[MichaelHatherly]

Ok, I'm subscribed to failures so between us it should be sufficient.

[ChrisRackauckas]

This did not remove the libgit2 dep?