Change BulkCreate ApplicationAuthentication logic to work with DB-backed DAO

[lindgrenj6]

BulkCreate wasn't working for applicationAuthentications before mostly because of our DB schema being not-correct for the vault backend.

In the future we're going to need to relax the constraints and change that table's layout a bit to fit both options. But today is not that day since we do not have a vault.

[MikelAlejoBR]

Hang on a minute. I was curious about the following change:

- VaultPath string `json:"vault_path"`
+ VaultPath string `json:"vault_path" gorm:"-"`

Since I remember I had to add it back because some tests are failing. And even though the CI says everything is right... If I issue the go test ./... -integration command locally, I get a test failure in the DAO package....

--- FAIL: TestDeleteApplicationAuthentication (0.19s)                                                                                                                                                                                       
    application_authentication_dao_test.go:51: incorrect applicationAuthentication deleted. Want "complex uuid" in the authenticationUid field, got ""

And a panic from a dereference error in the status listener package. Can you please run the tests locally too with the above command and confirm that it's not just me?

In the meantime I'm going to investigate what's failing.

[MikelAlejoBR]

Since I remember I had to add it back because some tests are failing. And even though the CI says everything is right... If I issue the go test ./... -integration command locally, I get a test failure in the DAO package....

--- FAIL: TestDeleteApplicationAuthentication (0.19s)                                                                                                                                                                                       
    application_authentication_dao_test.go:51: incorrect applicationAuthentication deleted. Want "complex uuid" in the authenticationUid field, got ""

Regarding this error, it corresponds to the following code block:

sources-api-go/dao/application_authentication_dao_test.go

Lines 46 to 53 in e70a415

	{
	want := applicationAuthentication.AuthenticationUID
	got := deletedApplicationAuthentication.AuthenticationUID
	if want != got {
	t.Errorf(`incorrect applicationAuthentication deleted. Want "%s" in the authenticationUid field, got "%s"`, want, got)
	}
	}

It seems that when I wrote the test, I was using the UUID as an extra check to see if I was fetching the correct application authentication. I guess we can safely delete that code block.

[MikelAlejoBR]

And a panic from a dereference error in the status listener package. Can you please run the tests locally too with the above command and confirm that it's not just me?

Regarding this one, I've been reverting the main branch locally until the tests stopped failing, and it seems that the bug was introduced in the commit bfa0816, after merging the PR #168 .

I've opened a ticket so that we don't forget to change the CI command so that it includes all the tests: https://issues.redhat.com/browse/RHCLOUD-18699

---

Since it's unrelated to this PR I think it is safe merging this PR after the DAO test change.

[lpichler]

/retest

[lindgrenj6]

I went through and removed all refs to AuthenticationUID and VaultPath since those aren't actually in the DB. We can re-add them in if/when we get a Vault.