Fi 581 do not skip on capability check when no capability statement loaded

[arscan]

When in community edition, running the profile tests will skip if you haven't first run the capability sequence. This doesn't make sense in the context of the community edition. Change so that if no capability statement is loaded, we do not skip, because we do not know if they support or do not support a capability.

Submitter:

• This pull request describes why these changes were made
• Internal ticket for this PR:
• Internal ticket links to this PR
• Internal ticket is properly labeled (Community/Program)
• Internal ticket has a justification for its Community/Program label
• Code diff has been reviewed for extraneous/missing code
• Tests are included and test edge cases
• Tests/code quality metrics have been run locally and pass

Reviewer 1:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure
  where appropriate, and accomplishes the task's purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

Reviewer 2:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure
  where appropriate, and accomplishes the task's purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code