feat(ws): set status.pauseTime on workspace

[Adembc]

This PR populates the status.pauseTime on the Workspace:

• Set status.pauseTime to current Unix epoch when paused.
• Reset status.pauseTime to 0 when unpaused.

[thesuperzapper]

This can be simplified:

Suggested change

	if workspace.Spec.Paused != nil && *workspace.Spec.Paused {
	if !*workspace.Spec.Paused {

[jiridanek]

really? https://go.dev/play/p/36NkL4Ra68g

package main

import "fmt"

type Spec struct {
	Paused *bool
}

func main() {
	var spec Spec
	if !*spec.Paused {
		fmt.Println("We're paused and there's some details here")
	}
}

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x480410]

goroutine 1 [running]:
main.main()
	/tmp/sandbox2639457518/prog.go:13 +0x10

Program exited.

[thesuperzapper]

@jiridanek yes, this is fine, because the Kubernetes version will always populate the field with false if not specified, because we set +kubebuilder:default=false:

notebooks/workspaces/controller/api/v1beta1/workspace_types.go

Lines 34 to 37 in e4e0aff

	// if the workspace is paused (no pods running)
	//+kubebuilder:validation:Optional
	//+kubebuilder:default=false
	Paused *bool `json:"paused,omitempty"`

[thesuperzapper]

@Adembc can you please add a unit test.

[Adembc]

I have added unit tests to ensure the pause time is correctly set.
Please review it @thesuperzapper @jiridanek

[thesuperzapper]

@Adembc thanks for your work on this, I have rebased this PR and made the following changes in def97ba

• Used the ~ operator with a tolerance of 5 seconds when ensuring the status.pauseTime is correctly set
• Use the global timeout and interval settings for all the Eventually( methods on workspaces/controller/internal/controller/workspace_controller_test.go

[thesuperzapper]

I am going to merge this now, since all the tests are passing.

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: thesuperzapper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thesuperzapper]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment