API context propagation

[Lenart12]

This pull request includes several changes to improve context handling and (and little logging). The most important changes include adding context propagation to API responses, introducing a logging function to show request details, and simplifying error handling in BLE control operations.

This PR will most importantly allow stopping command execution quickly if request is canceled. This will speed up queue processingby quite a bit if there is a lot of canceled requests and so prevent the queue from growing.

[Lenart12]

Small demo :^)

Screen.Recording.2025-01-13.145900.mp4

[wimaha]

Thank you for the PR!

What is with following commands reusing the same connection? The cancle would not work for them.

[Lenart12]

Context is based for each command on its own. If first command succeedes inside its allowed deadline, it will call operateConnection and then all following commands within it have its own context as it calls ExecuteCommand and inside that function the context is unpacked from apiResponse.

TeslaBleHttpProxy/internal/ble/control/control.go

Lines 284 to 292 in 499b868

	var ctx context.Context
	if command.Response != nil && command.Response.Ctx != nil {
	ctx = command.Response.Ctx
	} else {
	log.Debug("no context provided, using default", "command", command.Command, "body", command.Body)
	var cancel context.CancelFunc
	ctx, cancel = context.WithTimeout(context.Background(), 10*time.Second)
	defer cancel()
	}

[wimaha]

Thanks, the last Commit was very important.
I will approve the PR and will push a new version to the dev tag. Since I'm from now on 4 weeks away I don't want to push an update with so many changes because I can't change anything for 4 weeks.

Hope this is fine with you.