Split ctfd_challenge in two separate resources

[pandatix]

After #133, this PR would introduce breaking changes.
The reflection behind it comes from #131.

Inside this PR I drop ctfd_challenge in favor of 2 new resources:

• ctfd_challenge_standard
• ctfd_challenge_dynamic

Additionally to the features discussed in the issue (TL;DR better documentation, maintainability, and autocompletion), the internals changed toward a better fit of the CTFd API, and ease development of other providers for plugins.
For instance, when conceiving the Terraform provider for the ctfd-chall-manager plugin we would be able to reuse the ChallengeStandardResourceModel structure and ChallengeStandardResourceAttributes variable, in the way I implemented the ctfd_challenge_dynamic.

Reusing the ID for other resources (e.g. ctfd_file, ctfd_flag) is still possible.

Poke @Nishacid. I know you used it for GreHack24, your feedback on such an evolution would be welcome 😄

[coveralls]

Pull Request Test Coverage Report for Build 12526529544

Details

• 352 of 517 (68.09%) changed or added relevant lines in 7 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-2.4%) to 67.62%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
provider/challenge_common.go	9	15	60.0%
provider/challenge_standard_data_source.go	9	17	52.94%
provider/challenge_dynamic_data_source.go	87	125	69.6%
provider/challenge_dynamic_resource.go	210	323	65.02%

Files with Coverage Reduction	New Missed Lines	%
provider/utils/utils.go	2	94.44%

Totals
Change from base Build 12471534166:	-2.4%
Covered Lines:	1608
Relevant Lines:	2378

---

💛 - Coveralls

[NicoFgrx]

LGTM